Component Registry¶
| Working name | Type | Purpose | Status | Aliases / former names |
|---|---|---|---|---|
| Idea Ledger | System | Preserve and develop intentionally marked thoughts from AI conversations. | v0 test bed | IL |
| Idea Card | Information object | Hold a capture, its immutable source, interpretations, results, and future associations. | Implemented, terminology adopted | Ledger Entry rejected |
| Card Summary | Interface component | Provide a compact, searchable representation of an Idea Card. | Implemented | Record row |
| Card Detail | Interface component | Present the complete available content of one Idea Card. | Implemented | Detail popup |
| Source Record | Data component | Preserve exact source wording and provenance without later rewriting. | Partially implemented | Immutable source |
| Capture Trigger | Interaction protocol | Mark a thought inline using IDE#, QUE#, or DEC#. |
Manual capture implemented | Trigger |
| Project Memory | Documentation system | Maintain distilled, accepted project knowledge in parallel with the Ledger. | Initial implementation | Documentation layer |
| EvenFlow | Presentation layer | Support uninterrupted capture, review, and development of thoughts in Idea Ledger. | Working title adopted; operational interface implemented | Operational Stream, Use Stream rejected |
| CramNGo | Presentation layer | Deliver short, contextual learning without interrupting the person's work in Idea Ledger. | Working title adopted; initial Handbook implementation | Learning Stream, LearnGo rejected |
| Early Bird Guide | Documentation component | Orient testers and direct adversarial feedback. | Initial implementation | — |
| Feedback Protocol | Protocol | Convert observations and criticism into traceable Idea Cards. | Initial implementation | — |
| Collaborative Agent Handoff | Coordination document | Give an incoming Agent accepted context and safe continuation rules. | Initial implementation | Collaborative Handoff |
| Adversarial Agent Handoff | Audit document | Give an independent Agent a read-only, evidence-bound challenge mandate. | Initial implementation | Adversarial Handoff |
| Cross-platform Capture Bridge | Integration component | Deliver marked captures from supported AI platforms into the Ledger. | Proposed | Chat-side bridge, MCP bridge |
| Capture Contract | Data protocol | Define exact source, trigger, offset, identity, revision, consent, and idempotency semantics shared by manual and bridged capture. | Core contract deployed; platform bridge proposed | Ingest contract |
| Schema Migration Runner | Storage capability | Apply ordered, recorded, non-destructive schema changes. | Version 2 deployed and rehearsed | — |
| Ledger Portability | Recovery capability | Export and restore a checksummed, identity-preserving private Ledger package. | Implemented and production-copy round-trip tested | Export / backup |
| Proposal Staging | Data capability | Keep unaccepted AI interpretations outside authoritative Card payloads and views. | Storage boundary deployed; acceptance workflow proposed | Proposal state |
| EvenFlow Layouts | Presentation capability | Compose shared visibility controls into Lean, Regular, and Review layouts without changing stored data. | Implemented; device-local preferences | Display presets; Haul Ass and Standard rejected |
| Capture Draft | Resilience capability | Preserve unfinished capture text and supporting fields on the current device until capture succeeds. | Implemented; device-local only | Draft recovery |
| Taxonomy | Classification capability | Relate Cards to reusable vocabulary terms without rewriting their Source Records. | Initial category vocabulary implemented | Tags |
| Projects | Association capability | Relate Cards to reusable Project identities while preserving legacy project text compatibility. | Initial relational implementation | PRJ routing |
| Views | Presentation capability | Apply reusable filters to the same Card collection without copying or moving Cards. | Initial All Cards, Intake, Open Questions, and Decisions views implemented | Drupal-style Views |
Every independently discussable addition receives a working name, type, one-sentence purpose, status, introduction date when known, aliases, and eventually supporting Idea Card identifiers.