docs(specs): competitive positioning + developer docs architecture - #82
Merged
Merged
Conversation
…tecture Ground the positioning in the current agent-memory and schema-governance landscape: registries (Confluent/Glue), migration tooling (Liquibase/ Flyway/Hibernate), agent-memory systems (Zep, Mem0, Letta, Cognee), data contracts, and graph schema governance (Neo4j GRAPH TYPE, SHACL). Claims split shipped vs in-delivery vs planned. New developer-docs-architecture spec sets the docs IA: concept-anchored, 15-minute quickstart with real coordinates, opt-in feature pages, README migration plan, and the per-PR docs contract.
… sections Rank remaining gaps by prevalence across the four surveyed memory services, each with its citation. Move convergent mechanisms to their own section framed as parallel arrival at the same solutions. Add candidate-modules (governed working memory per ArcMem, background consolidation, procedural memory) and orthogonal-research sections (GUM lineage, TMS/ATMS, ACT-R activation, provenance semirings, with the three strongest borrowing opportunities). Correct the write-time rejection claim: recoverable by re-extraction in principle, at LLM cost and without reliable reproduction.
Open with what DICE is; compare at the substrate level per system. Schema governance becomes one capability section corrected by a per-system fact-check: declaration is common, Graphiti validates against Pydantic models, Cognee flags non-conforming nodes, Neo4j GRAPH TYPE hard-rejects at write time as a general database feature. The claims that survive are narrower: no surveyed system versions its extraction schema or compares a declaration against the live store. Remove all delivery status and PR references.
competitive-positioning.md derives from what main states, drops the material that only exists on unmerged branches, and corrects four claims that were wrong against the code. developer-docs-architecture.md becomes readme-to-docs-tree.md: the docs/ layout, which README section lands on which page, the concept and feature page shapes, the quickstart, the compatibility matrix, and the docs rule for feature PRs.
jimador
force-pushed
the
docs/positioning-and-docs-ia
branch
from
September 2, 2026 20:36
a344cf6 to
43b3bc8
Compare
igordayen
approved these changes
Sep 2, 2026
7 tasks
Budget policy sits above DICE because embabel-agent owns the budget, not because a host has to build one. Multimodal input already exists upstream, so the out-of-scope line says what is actually left. Docs follow the framework and use AsciiDoc.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Breaking changes: none. Specs only; no code, no API.
Two specs, both rewritten in this round.
specs/competitive-positioning.md: what DICE is against Zep/Graphiti, Mem0, Letta, Cognee, Hindsight, LangMem, Neo4j agent memory, and the three managed memory services, on the unit of knowledge, projections, knowledge hygiene, schema governance, shared mechanisms, remaining gaps, candidate modules, and orthogonal research. Every claim derives from whatmainstates (README,docs/design) with anchored citations; material that only exists on unmerged branches was removed, and four claims that were wrong against the code were corrected (valid-time fields exist, so the gap is transaction time; bi-temporal is held by Zep; the pipeline is not serial and pinning exists; the +0.15/×0.7/×0.85 figures are decay adjustments). Open questions each carry a recommendation.specs/readme-to-docs-tree.md(replacesspecs/developer-docs-architecture.md): thedocs/layout, which README section (by line range) lands on which page, the concept-page order, the feature-page template with each opt-in surface's activation condition, the quickstart steps and constraints, the compatibility matrix axes, and the rule that every feature PR ships its docs page.