System Modeling Notes Overview
This folder contains standalone PluralBridge concept notes for system modeling, focus, and consent-aware collaboration patterns.
How to use this folder
- Treat these notes as working design ideas, not final policy or roadmap commitments.
- Read each note as standalone; no single file is the one “master” model.
- Use these notes to pressure-test architecture, API, and UI assumptions while design evolves.
File-by-file guide
| File | Purpose |
|---|---|
pluralbridge_focused_system_context_spine_note.md |
Spine-level concept note for separating focus, membership, and relationship shape from authority. |
pluralbridge_reference_model_direction_note.md |
Strategic direction note framing PluralBridge as a reference model for plural data portability and user-authored structure. |
pluralbridge_structural_model_examples.md |
Example catalog of valid structure patterns (single root, multiple roots, child/sibling/related, graph, archived, evolving). |
pluralbridge_therapist_concept_note.md |
Therapist/professional-facing concept framing for safety, consent, language, and non-gatekeeping boundaries. |
pluralbridge_privilege_contribution_grant_note.md |
Attributed contribution concept for member-to-member description updates using explicit grant metadata and audit-safe behavior. |
Suggested read order
pluralbridge_focused_system_context_spine_note.mdpluralbridge_structural_model_examples.mdpluralbridge_privilege_contribution_grant_note.mdpluralbridge_therapist_concept_note.mdpluralbridge_reference_model_direction_note.md
Shared design boundaries
- Relationship shape is descriptive; it does not grant authority by itself.
- Access comes from explicit membership, consent, or policy.
- Focus and fronting are related but separate concepts.
- Notes here are intentionally non-normative and may evolve as implementation matures.