Concept
Knowledge Graph
The Knowledge Graph connects canonical artifacts, principles, roles, chapters, organizations, events, decisions, and marketplace offerings into a navigable civic memory.
Domain Roadmap
Built as a structured preview surface, not a blank placeholder.
Relationship schema
Artifact linking
Operating Questions
What kind of thing is this node and who has authority over it?
Which relationships are factual, interpretive, provisional, or approved?
How do decisions remain traceable as the platform grows?
Next Build Commitments
The graph should preserve artifact identity and version history.
Relationships should be typed so meaning does not collapse into links alone.
Knowledge graph data should support future AI, search, governance, and education.
Prototype Modules
What this domain will contain first.
Each module is designed to become a real component, workflow, or data object in the platform.
Node
Artifact Node
Canonical documents, routes, profiles, events, and decisions.
Edge
Relationship Type
Authority, dependency, reference, contribution, and governance links.
Lineage
Decision Trail
How a principle moves from Foundation to platform behavior.
Explorer
Graph Browser
A civic map of concepts, people, institutions, and artifacts.
Knowledge Graph System
A source map connecting books, constitutions, domains, and civic artifacts.
The graph defines how Stewardship knowledge objects relate to one another before database persistence and semantic search are introduced.
- Nodes
- 7
- Links
- 6
- Scenarios
- 3
- Rules
- 4
Book I: Reality
Grounds public claims in evidence, constraints, tradeoffs, and honest limits.
FOUNDATION-001 Book I Reality
Book II: Understanding
Creates shared language, learning pathways, and explainable civic knowledge.
FOUNDATION-001 Book II Understanding
SEC-001 Stewardship Experience Constitution
Governs the interactive experience, portal domains, and user-facing stewardship workflow.
SEC-001 Stewardship Experience Constitution
Academy Curriculum System
Turns Foundation books into pathways, lessons, practices, and reviewable artifacts.
FOUNDATION-001 Book II Understanding
Events Calendar System
Models gatherings as accountable civic records with outcomes and follow-up owners.
FOUNDATION-001 Book IV Stewardship
Marketplace System
Publishes reviewed offerings with providers, trust levels, review basis, and use cases.
FOUNDATION-001 Book III Character
Chapter Launch Toolkit
Starter charter, role map, meeting rhythm, onboarding checklist, and first service plan.
SEC-001 Stewardship Experience Constitution
Graph Relations
governs
SEC-001 Stewardship Experience Constitution / Academy Curriculum System
The Academy is part of the Stewardship Experience System and must remain traceable.
teaches
Book II: Understanding / Academy Curriculum System
Academy pathways turn shared language into civic learning practice.
produces
Events Calendar System / SEC-001 Stewardship Experience Constitution
Events create decisions, evidence, and open questions that feed institutional memory.
reviews
Marketplace System / Chapter Launch Toolkit
Marketplace offerings require review basis, provider trust, and constitutional alignment.
supports
Chapter Launch Toolkit / Events Calendar System
The toolkit helps organizers create repeatable meeting and service rhythms.
traces-to
Book I: Reality / Marketplace System
Marketplace claims should identify use case, limits, review evidence, and risks.
Assistant Scenario Models
How do I start a local Stewardship chapter?
Start with the Chapter Launch Toolkit, choose a meeting rhythm, name open roles, and connect the chapter to an Academy orientation.
Guardrail: Do not invent legal status, official approval, or verified membership where records do not exist.
Which Academy pathway should a new organizer take first?
Recommend Shared Understanding first, then Stewardship and Service once the organizer can explain core terms and meeting practices.
Guardrail: Explain the recommendation with sources and preserve uncertainty when learner context is incomplete.
Can this tool be published in the marketplace?
Check the provider, trust level, use case, review basis, constitutional alignment, and whether the offering produces reviewable public value.
Guardrail: Never approve an offering without review status, provider identity, and traceable review basis.
Source-first answers
Answers should cite known artifacts, platform records, or clearly state that the record is not available yet.
Framework traceability
AI responses should connect advice back to Foundation books, constitutions, domain records, or review standards.
No false authority
The assistant must not claim approvals, memberships, legal conclusions, or verified facts absent a platform record.
Actionable next step
When possible, responses should point the user to a practical next record, pathway, event, or review action.