Taxonomy and Views¶

Idea Ledger separates classification from presentation. Taxonomy describes reusable relationships around a Card. Views select and arrange Cards without moving, duplicating, or rewriting them.

Initial taxonomy boundary¶

Schema version 3 introduces reusable Projects and a first vocabulary named category. A Card may relate to a Project and to multiple Categories. Project text from earlier Cards is migrated into the relational Project structure while the original compatibility field remains in place.

Categories entered by a person during manual capture are accepted classifications. AI-suggested classifications remain Proposals and do not enter ordinary Views until a future acceptance workflow exists.

The initial interface accepts comma-separated Categories. It intentionally does not yet provide vocabulary administration, merging, hierarchy, synonyms, or bulk reclassification.

Initial Views¶

• All Cards shows the current collection.
• Intake shows Cards with neither a Project nor a Category, providing an unassociated sorting queue.
• Open Questions shows unanswered Question Cards.
• Decisions shows Decision Cards.

These are composed queries over one Ledger. A Card can appear in several Views because a View is a lens, not a container.

Capability Composition boundary¶

Capture, storage, taxonomy, and Views remain independently discussable capabilities. Adding a View does not require another Card type or database. Adding a vocabulary does not alter the immutable Source Record. Future timelines and boards should consume these same associations rather than creating parallel truth.