Concepts
Collections, tags and portfolio
Choose types and dimensions without confusing organization with permission.
Typed collections
The collection describes an entry’s purpose. The 23 collections below come from the ontology reference; a planning collection does not execute the plan and a DAG definition does not promise automatic execution.
- rule — Rules
- instruction — Procedures
- fact — Verifiable facts
- learning — Lessons
- preference — Preferences
- decision — Decisions and context
- content — Reference content
- agenda — Schedules
- contacts — Contacts
- handoff — Context handoff
- roadmap — Planning
- files — File references
- docs — Documentation references
- dags — DAG definitions
- tools — Tool knowledge
- users — Identities and profiles
- session — Session state; requires session_id
- artifact — Artifacts; requires artifact_type
- compliance — Reviews; requires compliance_type
- semantic_log — Log packages; requires package_id
- product — Product identity
- project — Product demand
- initiative — Bounded delivery
Tag dimensions
The 11 dimensions organize context and access. audience controls reading; editors controls changes. person describes relevance, not access. project identifies the physical workspace, while prod, proj and init organize the portfolio.
- skill — Skill
- agent — Agent
- domain — Technical domain
- project — Physical workspace
- situation — Situation
- person — Mentioned person
- audience — Who may read
- editors — Who may edit
- prod — Product
- proj — Product project
- init — Initiative
Priority, scope and source
Priorities are critical, high, medium and low. Scopes are global, project and session. Source may be human, agent or system, but writing that label does not replace authentication. Portfolio links product → project → initiative; the hierarchy does not expand ACLs.