Readable operating context
Company and project views organize status, timelines, decisions, people and open items into a Markdown vault.
Source-backed project memory and company operating briefs that make ongoing work easier for people and coding agents to pick up.
Implemented operational evidence aggregation, narrative and question workflows, alongside canonical project-context tooling.
Decisions, open work and recent changes are scattered across repositories, documents, meetings and task systems, while agent sessions need consistent project context.
Built complementary evidence-collection and project-workspace tools that turn repositories, meetings and task history into readable operating briefs, inspectable answers and reusable agent context. Separate graph and planning helpers expose relationships, open work and effort estimates.
Enables company-wide and project-scoped orientation, cited answers and repeatable context refreshes without hiding missing sources. This is an implemented tooling family, not a claim of one integrated hosted platform.
Company and project views organize status, timelines, decisions, people and open items into a Markdown vault.
Retrieval tools, source citations and explicit unavailable-source handling keep answers inspectable.
Project selection, API-based staging and schedule-safe synchronization support curated multi-project rollups.
Related tools provide source-linked graph views, follow-up triage plans and historical effort estimates; these are inspectable planning aids, not guaranteed forecasts or an autonomous delivery service.
Evidence ingestion, SQLite extraction/retrieval and narrative materialization are separate from workspace installation and publication. The repositories are complementary tools; a direct runtime integration is not established.
Talk with me about the product, the engineering and the decisions that need to stay with people.