Skip to content
d8p

Menu

Site controls

The problem: useful context did not reliably survive

The earliest version was a toolkit. An October 6, 2025 record describes calendar capture, research scraping, note templates and day-planning tools in one workspace. Each addressed a friction in my own practice.

The toolkit grew into Sage. By early 2026, I could interact through a development environment or Slack on my phone. The historical narrative describes a continuity problem: a conversation on a walk did not reliably carry into work at the desk. The interfaces shared a name without sharing enough context.

I began separating the assistant’s identity and memory from the interface. Conversations needed provenance. A decision needed to remain available when the session changed. The practical question became: what must the next interaction understand to continue responsibly?

The decision: give each part a clear job

As Sage grew, one repository carried knowledge, integrations, publishing, instructions, project history and operational tools. The next structure separated those responsibilities into a network of specialized repositories, while retaining Sage as a historical reference.

That separation carries a tradeoff. Clearer ownership makes a change easier to locate and review, but the handoff between repositories becomes something the system must define and maintain. Shared conventions cannot substitute for an actual interface or a verified result.

The architecture distinguishes five responsibility layers from an execution flow. Scaffold supplies shared conventions; platform capabilities support reusable work; domain repositories own specialized work; administration supports daily operations; management connects priorities, decisions and delivery evidence.

These are defined responsibilities. They do not establish that an autonomous local steward operates in every repository or that cross-repository orchestration is deployed. The case concerns my integration and application of established practices, not invention of repository networks, typed interfaces or review gates.

Presentation notes

Read the chapter for the decision, evidence and its limits.