Skip to content

Organizations

This page has moved

What was once an organization is now called a spine definition, and its documentation has been folded into Spines. See Spines → The spine definition for the registry, the proposed/spine states, storage, and the lifecycle operations (promote, demote, resync, verify, delete).

The concept is unchanged — a named, owner-scoped definition of how to arrange the corpus, held in one of two states — only the name is settled. Follow the link above; the registry file keeps its historical name (organizations.py).

Design notes

The decisions behind this, drawn as a slice of the memory tree.

  • D Organizations storage + owner-level navigation architecture (Phase 1a–1d)active
    An Organization is a first-class, owner-scoped (project OR graph) matrix definition — a row axis + ordered typed columns — decoupled from any single review.
  • D Organizing principle: semantic base -> spine -> matrix (two kinds of uniting)active
    The canonical conceptual model for the whole zettelkasten organization layer.
  • D Row axes: drop persona, add greyed-out 'spine' axis; materialize-spine flow surfaced in Previewactive
    Design decisions from user feedback while testing the matrix wizard:
  • D Prune orphaned non-enforcing keyed meta for unused/demoted spinesactive
    Post-1.3.1 follow-up: closed the documented DEFERRED LIMITATION where materialize_structure writes a structure-only (non-enforcing) keyed block onto each source OPTIMISTICALLY, before reconcile decides membership.
  • R Angelo
    • P zettelkastenactive
      • P Phase 2: Literature Review Systemactive
        • P Workshop tab: Reading Syllabus (learn) + claim-centric Review/Outline (write)active
          • P Organizations: project-level lenses + spines (matrix builder redesign)active
            • D Organizations storage + owner-level navigation architecture (Phase 1a–1d)active
              • C Checkpoint: Organizations Phase 1a–1d complete + verified
            • D Row axes: drop persona, add greyed-out 'spine' axis; materialize-spine flow surfaced in Previewactive
            • P Spines as the primary organization mechanism (spine directory + default lens + embedded schema)active
              • P Phase: Graph D-phase3 — spine-sourced extraction (scribe reads embedded schema + spine_ref structure; spine scope; spine-member attach)active
                • P Deferred spine affordances: multi-spine extraction + tag_stamp route + per-doc spine routingactive
                  • D Prune orphaned non-enforcing keyed meta for unused/demoted spinesactive
            • P Schema matrix views (ephemeral hub) + user-facing Spines renameactive
              • D Organizing principle: semantic base -> spine -> matrix (two kinds of uniting)active

Semantically related entries from the memory graph.