aSPARK-memory
Architectural decisions and organizational lessons as durable engineering memory.
The graph knows what was built. It does not know why it was built that way. That is the gap memory closes: ADR and decision memory, historical context — anchored to the graph nodes they explain.
The intelligence services build on it: decision recall, risk prediction, standards feedback. All three as consumers of versioned data, never a bypass of the gates.
- ◆
ADR and decision memory
Architectural decisions stay findable, together with the context they were made in.
- ◆
Anchored to the graph
A decision hangs off the nodes it explains — not in a separate wiki that drifts over time.
- ◆
Intelligence services
Decision recall, risk prediction, standards feedback — consumers of versioned data, never a bypass of the gates.
This product is future work — the last item on the roadmap, deliberately: memory without a graph would have nothing to anchor to.
Each product has one responsibility and stable interfaces. A weakness in one must never require changes in another.
Does this fit your delivery process?
Start with Core on a pilot project. The workflow, knowledge graph and policy packs are all open on GitHub.
No public repository yet.