## Active Plans

Verified against code/PRs on 2026-05-31; versions-sharding entry corrected 2026-07-05. Plans with real remaining work:

- [Agent Memory Leaderboard entry](/plans/agent-memory-leaderboard.md); enter demarkus in agentmemoryleaderboard.ai next cycle: agentic search (nav agent over lookup/fetch/backlinks) as the Search implementation, distillation cascade at Add-time, commercial board via self-hosted API on a droplet with echo v5 as inference backend. Sub-project hub: [/memoryleaderboard/](/memoryleaderboard/index.md) (repo `/Users/fritz/latebit/memoryleaderboard`). **Planned 2026-08-13; cycle 1 closed 2026-08-07, awaiting cycle 2 dates. Phase 0 (recon) not started.**
- [Code Quality Sweep 2026-08](/plans/code-quality-sweep-2026-08.md); full-repo review findings (6-agent sweep, 2026-08-12): 10 high-severity correctness/security leads, cross-module duplication extraction targets, broker package-split recommendation, dead code, pervasive rule violations, remediation order. **Findings recorded; nothing fixed yet.**
- [Bucket Document-Store Backend](/plans/bucket-store.md); native object-storage backend (GCS first, S3/MinIO designed-for) as a third DocumentStore implementation, enabling multi-replica worlds on k8s with no PVCs: per-document manifest objects committed via generation CAS, write-once version blobs, per-pod LIST-driven hash-index/catalog sync, `storage.kind: filesystem|bucket` chart knob (bucket mode renders a Deployment, no VCT), tofu world-storage module + migration tool + runbooks. **Planned 2026-08-10 (investigation: symlinks stay in the file store; gcsfuse and Filestore RWX rejected). Not started; 8 PRs.**
- [demarkus as a service](/plans/demarkus-as-a-service.md); the hosted offering: Aiven adjacent service model, three tiers matching the website's Personal, Team, and Knowledge System scales, VPS first substrate with Kubernetes only on overflow, per world billing with the box as the size step, power off instead of scale to zero, and a management app as the only new engineering. **Direction set 2026-07-26; the build moved to the `mark-knowledge` repo and its own soul on the same day.** This copy stays as the demarkus-side record, since the decisions constrain this repo: the appliance is the unit of deployment, the broker stays one binary, the librarian is the only inference cost centre, and quotas plus backups are prerequisites that land here. Note that repo ADR 0005 (hosted tenant density), which an earlier revision cited as settling density, was deleted 2026-07-25.
- [Knowledge Ingestion Pipeline](/plans/knowledge-ingestion.md); narrative + design for how org knowledge flows into a knowledge destination, framing the soul as the staging/write-ahead tier and the knowledge destination as the curated read-model, with one curation gate (cascade model routing: Haiku triage → strong-model distillation → human approval) reused across all inflows (soul promotion, Confluence, Slack, Jira, meetings). Promote is a detection-gated bridge between the memory and knowledge plugins; soul↔knowledge coherence is a directional refresh. **Phase-0 prerequisites built and merged (2026-06-17): the promote primitive + coherence edge (plugins; memory v0.6.0 / knowledge v0.2.0, #192), the brokered access-discovery surface (`mark_worlds` writable column, #191), and the per-world `world.md` descriptor. Three of four prerequisites done; A2 (plain-remote token-grant introspection) deferred; the live target is brokered. Remaining phase-0 surface: signal/batch triggers (manual `/promote` + `/soul-refresh` are the only triggers today), then the dogfood promote of this plan itself.**
- [Universe Library](/plans/universe-library.md); web front-end for a demarkus universe (Go + htmx reading room). Sub-project hub: [/demarkus-library/](/demarkus-library/index.md). **Reading room feature-complete and deployed (cluster library 0.5.2); see the sub-project [roadmap](/demarkus-library/roadmap.md).**
- [Universe Deployment (Phase 6)](/plans/universe-deployment.md); Helm charts (server, broker, agent), OIDC token broker, release pipeline, observability. ~95% complete (PRs #126-#134, 2026-05-14). Remaining §6.6 (docs) + §6.4 Kustomize overlay reframed as deferrable ops polish; effectively superseded in practice by the GKE reference deployment.

## RFC Review

- [Demarkus / Knowledge System FAQ](/rfc-review-faq.md); terse Q&A for the RFC review session, sourced from the demarkus and demarkus-knowledge-system-deploy repos. **Status: WIP, pending review via the library.**