A governed artifact graph is reusable.
Governed context architecture
Artifact Graph
A page becomes durable when its sources, claims, receipts, validators, and related artifacts are traversable.
A SharePlane artifact is not just a finished page. It is a node in a governed graph: source dossier, claim ledger, evidence posture, related artifacts, deterministic validation, receipts, registry metadata, and human approval. The graph is what lets context compound without turning a chat thread, model, agent, or runtime into the authority layer.
The artifact graph makes durable context inspectable. A human can read the argument. An agent can traverse the source and claim structure. A maintainer can validate the page and find the receipt. An approval gate can decide what is accepted without pretending the tool layer owns truth.
repo-derived
architecture judgment
public-safe
validator-backed
Source dossierorigin, authority, caveat
Claim ledgerassertion and posture
Evidencesupport and bounds
Validatordeterministic checks
Artifact nodereadable public-safe page
Receiptmaintenance memory
Registrycatalog projection
Approval gatehuman authority boundary
TLDR
The page is the node. The edges carry authority.
The artifact node holds the readable thesis. The edges carry source posture, claim posture, validation, receipt history, related context, and approval state.
The registry is a catalog projection, not a runtime database.
Validators prove required structure and exclusions. They do not prove taste or universal truth.
Runtime systems can come later only after the artifact plane proves what context is worth operationalizing.
One-minute brief
What changed, why it matters, and reader payoff.
The durable unit is not the chat answer, prompt, model, or agent run. The durable unit is the public-safe artifact plus the governed edges that explain where it came from, what it claims, what supports it, what validates it, and who accepted it.
Without graph edges, artifacts become isolated pages. With governed edges, the library becomes traversable context: readers can inspect confidence, agents can retrieve boundaries, and maintainers can update without guessing why the page exists.
You can evaluate an artifact by following the graph: source dossier first, claim ledger second, validator third, receipt fourth, related artifacts fifth, approval boundary last.
Thesis reading view
The graph is the product surface beneath the page.
A finished page is the visible surface. That matters because humans need a coherent reading path. But the page alone is not enough. Without a source dossier, claim ledger, validation path, receipt, and related-artifact map, the page becomes another polished object that future humans and agents must re-interpret from scratch.
The artifact graph solves that by making the surrounding context explicit. The source dossier tells readers what the artifact is grounded in and what it is not. The claim ledger separates repo-governance facts, owner-approved thesis, architecture judgment, teaching interpretation, caveat, and validation posture. The receipt records how the artifact was implemented and validated. Related artifacts show where the idea sits in the broader SharePlane library.
This is why the graph is not a database, vector store, RAG layer, or autonomous runtime. Those may become useful later. The graph begins as static, inspectable, source-controlled structure. It is boring on purpose, which is usually how durable systems avoid becoming expensive confetti cannons.
The practical rule is simple: publish one artifact, but do not strand it. Give it source edges, claim edges, validation edges, receipt edges, related-artifact edges, registry edges, and an approval gate. That turns a page into context that can be maintained.
The graph does not replace judgment. It routes judgment to the right place.
Graph anatomy
A governed graph has nodes, edges, and gates.
The hero diagram and the anatomy map use one central artifact node, governed edge types, relationship rails, claim/source/validator/receipt paths, and explicit traversal routes.
Artifact node plus governed edges
Artifact nodethe readable public-safe page.
Source edgewhere the artifact came from and how the source should be read.
Claim edgewhat the artifact asserts and with what posture.
Evidence edgewhat supports, bounds, or caveats a claim.
Validator edgewhat deterministic checks passed and what they cannot prove.
Receipt edgewhat changed, where, when, and under which boundary.
Related artifact edgehow this artifact connects to adjacent context.
Registry edgehow the catalog projects the artifact for discovery.
Approval gatewhere human acceptance and merge authority live.
If a future reader cannot follow the edge, the artifact is not ready to compound.
Edge taxonomy
Edges are not decoration.
Edges are not decoration. Each edge has a job. If the job is unclear, the graph becomes a diagram-shaped excuse for confusion, a traditional human specialty.
identifies origin, authority, public-safe boundary, and caveat.
states what is being asserted and whether it is fact, thesis, interpretation, judgment, caveat, or speculation.
points to repo support, external support when scoped, or related artifact support.
records deterministic checks and prohibited-material exclusions.
preserves implementation and maintenance history.
shows adjacency, dependency, contrast, or precedent.
makes the artifact discoverable without turning the catalog into the source of truth.
shows that acceptance belongs to human review, not the model, agent, UI, or validator.
Traversal paths
Different readers traverse the graph differently.
thesis, one-minute brief, graph anatomy, claim ledger, related artifacts.
anchors, semantic headings, source dossier, claim IDs, registry metadata, receipt path.
validator, receipt, registry entry, related artifacts, source boundary.
claim posture, caveats, visual precedent, acceptance criteria, exact-head merge boundary.
Source dossier
Repo-derived, public-safe, not external research.
This artifact is repo-derived. It uses SharePlane standards, current registry metadata, adjacent published artifacts, and artifact-publication learning receipts as its source base. It does not add external public sources and does not publish private source material.
SharePlane README and operating docs
- Source type
- repo-governance documentation.
- Why it matters
- defines SharePlane as static, reader-first, artifact-first, and not an AI runtime.
- Claims supported
- static-first boundary, operating model, publication boundary.
- Confidence contribution
- high for repo posture.
- Caveat
- repo authority only, not external proof.
SharePlane artifact standard and implementation prompt
- Source type
- artifact implementation standard.
- Why it matters
- defines Creative Lock, no-regression gate, registry scope, source dossier, claim ledger, prompt suite, and Codex boundaries.
- Claims supported
- required artifact structure and implementation constraints.
- Confidence contribution
- high for artifact requirements.
- Caveat
- standard governs SharePlane artifacts, not all publishing systems.
Provenance and visual prompt standards
- Source type
- reusable standards.
- Why it matters
- separates public source framing from internal receipts and defines prompt suite quality.
- Claims supported
- reader-facing provenance, prompt suite structure, forbidden metadata labels.
- Confidence contribution
- high for this artifact's UX rules.
- Caveat
- does not prove generated-image quality.
Artifact publication learning log and negative-pattern receipt
- Source type
- workflow learning record.
- Why it matters
- records what failed during the Context Is the Product cycle and what future agents must avoid.
- Claims supported
- no-regression posture, validator boundary, visual quality lesson.
- Confidence contribution
- high for future-agent correction rules.
- Caveat
- negative patterns are correction guidance, not approved implementation patterns.
Context Is the Product
- Source type
- adjacent published thesis artifact.
- Why it matters
- parent thesis for governed context, artifact graph, claim ledger, validation, receipts, and approval gates.
- Claims supported
- semantic parent concept.
- Confidence contribution
- medium-high for SharePlane architecture thesis.
- Caveat
- accepted floor, not future visual bar.
When Execution Gets Cheap, Advantage Moves
- Source type
- visual and UX precedent.
- Why it matters
- establishes the quality baseline for article lane, source dossier, claim posture, prompts, and theme behavior.
- Claims supported
- visual precedent and no-regression baseline.
- Confidence contribution
- high for local artifact quality comparison.
- Caveat
- source topic differs from Artifact Graph.
Claim ledger
Claims stay separate from posture, support, and caveat.
Rows distinguish repo/source support, related artifact support, owner-approved architecture thesis, caveat or unresolved boundary, and deterministic validation support.
| Claim ID | Claim | Repo/source support | Related artifact support | Posture | Confidence | Caveat |
|---|---|---|---|---|---|---|
| artifact-node | The readable artifact is the visible node in the graph. | README, artifact standard, implementation prompt. | Context Is the Product. | repo-governance plus teaching interpretation | high | A page alone is not the whole context plane. |
| governed-edges-carry-authority | Source, claim, validation, receipt, related-artifact, registry, and approval edges carry durable authority context. | Artifact standard, provenance standard, learning log. | Context Is the Product. | architecture judgment | medium-high | The edge model is SharePlane architecture, not universal law. |
| source-dossier-before-claim | Reader trust improves when source posture is visible before claims are treated as reusable context. | Provenance standard, artifact standard. | When Execution Gets Cheap, Context Is the Product. | repo-governance | high | Does not prove every source is externally true. |
| claim-ledger-is-traversal-index | A claim ledger lets humans and agents traverse what is asserted, supported, caveated, or unresolved. | Artifact standard, implementation prompt. | Context Is the Product. | architecture judgment | medium-high | A ledger still requires human judgment. |
| validator-edge-is-necessary-not-sufficient | Validators can prove required structure and exclusions, but not taste, truth, or strategic correctness. | Learning log, negative-pattern receipt, artifact standard. | Context Is the Product. | validation posture | high | Owner review remains required. |
| receipt-edge-preserves-maintenance-memory | Receipts preserve implementation and validation context for future maintainers and agents. | Provenance standard, implementation prompt. | All registry-backed artifacts with receipts. | repo-governance | high | A receipt is only useful if accurate and maintained. |
| approval-gate-is-authority-boundary | Human approval gates decide acceptance and merge authority. | README, AGENT_INDEX, workflow decision tree. | Context Is the Product. | repo-governance | high | Approval does not imply external truth. |
| registry-is-catalog-projection | The registry projects discovery metadata; it is not the source of truth for the whole artifact graph. | README, registry metadata, artifact standard. | Agent-Readable Web, Context Is the Product. | architecture judgment | medium-high | Registry changes must be scoped and surgical. |
| runtime-later-not-authority-now | Runtime systems can come later only after the static artifact plane proves what context is worth operationalizing. | README, artifact standard, negative-pattern receipt. | Context Is the Product, LLM Wikis. | architecture judgment | medium-high | Future runtime work requires a separate scoped lane. |
Visual prompt suite
Copy-ready prompts with visible text constraints.
Each prompt specifies format, visible text constraints, visual grammar, alt-text concept, and negative constraints. Prompts explicitly prevent visible metadata labels such as prompt, metadata, layout notes, aspect ratio, and alt text.
Mainline white 16:9
Premium light-background editorial systems diagram.
Create a premium 16:9 light-background editorial systems diagram titled `Artifact Graph`.
Artifact context: this is a SharePlane artifact about a durable artifact graph. It shows one public artifact page becoming durable through governed edges: source dossier, claim ledger, evidence, validator, receipt, registry, related artifact, and human approval.
Concept purpose: explain that the page is only the visible node; authority is carried by explicit relationships around it.
Reader takeaway: the artifact becomes reusable context because its source, claim, evidence, validation, receipt, registry, related-artifact, and approval edges are visible and governed.
Visible labels: `Artifact node`, `Source dossier`, `Claim ledger`, `Evidence`, `Validator`, `Receipt`, `Registry`, `Related artifact`, `Human approval`.
Visible bottom-line banner: `A page becomes durable when its edges are governed.`
Semantic mapping: place the artifact node at center as the page. Map source dossier to origin and review basis. Map claim ledger to stated claims and caveats. Map evidence to supporting material. Map validator to deterministic structure checks. Map receipt to maintenance memory. Map registry to catalog metadata. Map related artifact to reuse path. Map human approval to the final authority gate.
Visual grammar: precise editorial architecture map on a warm drafting-table background. Use restrained black, charcoal, warm white, graphite, and one controlled approval mark. Use thin rule lines, labeled rails, crisp spacing, and quiet hierarchy. The diagram must read as a governance system, not a social network.
Governance boundary: do not imply runtime AI, a database, a vector store, a RAG layer, an autonomous agent, external proof, or a universal architecture mandate.
Text constraints: render only the title, visible labels, and bottom-line banner. Do not render prompt metadata labels.
Forbidden metadata labels: do not render `prompt`, `metadata`, `layout notes`, `aspect ratio`, `alt text`, `artifact context`, `concept purpose`, `reader takeaway`, `semantic mapping`, `governance boundary`, `text constraints`, `negative constraints`, or `forbidden metadata labels`.
Negative constraints: no generic AI futurism, no neon mesh, no faux dashboards, no random network wallpaper, no stock icons, no unreadable microtext, no prompt metadata labels, no random AI circuitry, no 3D blobs, no fake terminal panels, no spreadsheet UI, no busy decorative nonsense.
Accessibility alt-text concept: a central SharePlane artifact page connected to governed source, claim, evidence, validation, receipt, registry, related-artifact, and human-approval edges so non-visual readers understand how the page becomes durable.Dark expressive 16:9
Technical systems map with distinct edge rails.
Create a premium 16:9 dark technical editorial graphic titled `Governed Artifact Graph`.
Artifact context: this is a SharePlane artifact about a durable artifact graph. It shows a SharePlane page becoming reliable context through governed edges: source dossier, claim ledger, evidence, validator, receipt, registry, related artifact, and human approval.
Concept purpose: make the edge system legible as the authority layer around the artifact, not as a runtime or storage diagram.
Reader takeaway: the central artifact is not self-authorizing; source, claim, evidence, validation, receipt, registry, related-artifact, and approval edges explain why it can be trusted, reused, and maintained.
Visible labels: `Source edge`, `Claim edge`, `Evidence edge`, `Validation edge`, `Receipt edge`, `Registry edge`, `Related artifact edge`, `Approval edge`.
Visible bottom-line banner: `Do not put authority in the runtime layer.`
Semantic mapping: place one bright artifact node at center. Map source edge to source dossier, claim edge to claim ledger, evidence edge to support, validation edge to validator, receipt edge to publication memory, registry edge to catalog metadata, related artifact edge to adjacent pages, and approval edge to human authority.
Visual grammar: black and graphite field-map aesthetic with a central off-white artifact node and eight labeled edge rails. Make approval the strongest gate. Distinguish the other edges through line weight, spacing, and shape, not rainbow color chaos. The design should feel like a serious systems map for architecture review.
Governance boundary: do not imply runtime AI, a database, a vector store, a RAG layer, an autonomous agent, external proof, or a universal architecture mandate.
Text constraints: render only the title, visible labels, and bottom-line banner. Do not render prompt metadata labels.
Forbidden metadata labels: do not render `prompt`, `metadata`, `layout notes`, `aspect ratio`, `alt text`, `artifact context`, `concept purpose`, `reader takeaway`, `semantic mapping`, `governance boundary`, `text constraints`, `negative constraints`, or `forbidden metadata labels`.
Negative constraints: no generic AI futurism, no neon mesh, no faux dashboards, no random network wallpaper, no stock icons, no unreadable microtext, no prompt metadata labels, no cyberpunk city, no fake hologram dashboard, no glowing brain, no robot hands, no decorative circuit wallpaper.
Accessibility alt-text concept: a dark systems map showing a SharePlane artifact surrounded by governed source, claim, evidence, validation, receipt, registry, related-artifact, and human-approval edges, with authority kept out of the runtime layer.Capstone 16:9
One artifact, many governed edges.
Create a premium 16:9 dark editorial principle graphic titled `One Artifact, Many Governed Edges`.
Artifact context: this is a SharePlane artifact about a durable artifact graph. It presents one artifact becoming durable through governed edges: source dossier, claim ledger, evidence, validator, receipt, registry, related artifact, and human approval.
Concept purpose: turn the page thesis into a memorable capstone: durability comes from governed relationships, not from page polish alone.
Reader takeaway: context compounds when the artifact keeps its source basis, claims, evidence, validation, receipts, registry projection, related paths, and approval boundary attached.
Visible labels: `One artifact`, `Source dossier`, `Claim ledger`, `Evidence`, `Validator`, `Receipt`, `Registry`, `Related artifact`, `Human approval`.
Visible bottom-line banner: `The graph is how context compounds.`
Semantic mapping: render the artifact as one central page. Map source dossier to a reference card, claim ledger to an evidence table, evidence to support marks, validator to a check rail, receipt to a provenance slip, registry to catalog metadata, related artifact to a linked page, and human approval to a deliberate gate.
Visual grammar: near-black capstone board with premium editorial restraint, strong negative space, precise alignment, off-white typography, graphite rails, and one controlled approval mark. The composition should feel like a final principle slide, not a product diagram or dashboard.
Governance boundary: do not imply runtime AI, a database, a vector store, a RAG layer, an autonomous agent, external proof, or a universal architecture mandate.
Text constraints: render only the title, visible labels, and bottom-line banner. Do not render prompt metadata labels.
Forbidden metadata labels: do not render `prompt`, `metadata`, `layout notes`, `aspect ratio`, `alt text`, `artifact context`, `concept purpose`, `reader takeaway`, `semantic mapping`, `governance boundary`, `text constraints`, `negative constraints`, or `forbidden metadata labels`.
Negative constraints: no generic AI futurism, no neon mesh, no faux dashboards, no random network wallpaper, no stock icons, no unreadable microtext, no prompt metadata labels, no cathedral, no chisel, no fantasy architecture, no generic flowchart clipart, no fake app dashboard.
Accessibility alt-text concept: one SharePlane artifact page connected to governed source dossier, claim ledger, evidence, validator, receipt, registry, related-artifact, and human-approval edges, showing how context compounds without making the runtime authoritative.Mobile/social 9:16
Optional vertical variant for phone reading.
Create a premium 9:16 mobile editorial graphic titled `Artifact Graph`.
Artifact context: this is a SharePlane artifact about a durable artifact graph. It compresses the artifact into a phone-readable stack where governed edges make the page durable: source dossier, claim ledger, evidence, validator, receipt, registry, related artifact, and human approval.
Concept purpose: show the minimum mobile version of the same idea without losing the governance meaning.
Reader takeaway: authority lives in the governed edges around the page, not in a runtime layer or decorative network.
Visible labels: `Artifact`, `Source`, `Claim`, `Evidence`, `Validate`, `Receipt`, `Registry`, `Related`, `Approve`.
Visible bottom-line banner: `Authority lives in the edges.`
Semantic mapping: place the artifact near the top third. Stack source as source dossier, claim as claim ledger, evidence as support, validate as validator, receipt as publication memory, registry as catalog metadata, related as adjacent artifact path, and approve as human approval gate.
Visual grammar: vertical stacked map on a warm-white background with large labels, strong spacing, and phone-readable hierarchy. Keep the edge path clear from artifact to approval.
Governance boundary: do not imply runtime AI, a database, a vector store, a RAG layer, an autonomous agent, external proof, or a universal architecture mandate.
Text constraints: render only the title, visible labels, and bottom-line banner. Do not render prompt metadata labels.
Forbidden metadata labels: do not render `prompt`, `metadata`, `layout notes`, `aspect ratio`, `alt text`, `artifact context`, `concept purpose`, `reader takeaway`, `semantic mapping`, `governance boundary`, `text constraints`, `negative constraints`, or `forbidden metadata labels`.
Negative constraints: no generic AI futurism, no neon mesh, no faux dashboards, no random network wallpaper, no stock icons, no unreadable microtext, no prompt metadata labels, no generic mobile app mockup, no chartjunk, no tiny labels.
Accessibility alt-text concept: a vertical mobile diagram showing a SharePlane artifact connected to source, claim, evidence, validation, receipt, registry, related-artifact, and human-approval edges so the governance path remains clear on a phone.