Source
Keep the original material and its location.
Technology & professional services
Decisions that outlast the meeting.
Turn architecture records, client calls, tickets, code, and deliverables into a memory where every decision keeps its speaker, revision, and source.
Keep what changed, who changed it, and what the code now does.
Architecture decisions and meeting lines stay linked to the code and deliverables they shaped. Later reversals appear as explicit revisions, preserving the earlier record.
Source material
- Architecture decisions
- Meeting notes and email
- Tickets and code
- Client deliverables
Ontology relationships
- Decision ↔ revision
- Statement ↔ speaker
- Requirement ↔ deliverable
- Code ↔ rationale
From field evidence to agent action.
Ontology
Name entities and relationships in the field's own language.
Memory
Consolidate, recall, revise, and preserve provenance.
Action
Let agents work with an inspectable trail.
Workflows grounded in domain memory.
Architecture decision ledger
Read decisions in revision order and keep the reason behind the current architecture.
What remains verifiable
Superseded decisions remain linked to the current revision.
Client memory in their own words
Return the exact line, speaker, meeting, and source when a direction is questioned.
What remains verifiable
A screen-share can open the source line immediately.
Agent work grounded in rationale
Let the agent inspect the decision note behind a function before editing and verifying code.
What remains verifiable
Plans, edits, commands, and results stay inspectable.
