coulomb/content-explorer
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Freeze the v0.1 contract and the local ingest connector.

Browse source 
The snapshot and manifest schemas, both example dataspaces, and the shared text renderer now pass the fixture validator and the negative contract tests. JSON, NDJSON, and Markdown frontmatter publish a snapshot only when rights, identity, and references allow it. CONTENT-WP-0001 and CONTENT-WP-0003 are marked finished against those artifacts. CONTENT-WP-0000-T04 stays open. SCOPE.md and the 19:05 scope-against-intent note record the stop.

Assistant: grok
Assistant-Session: 01a130f1-abfb-7d71-9cd6-a8b75ec7f95a
This commit is contained in:
tegwick 2026-10-12 19:07:32 +02:00
parent 2b1706559b
commit 072a7fa550
30 changed files with 1896 additions and 264 deletions
Download patch file Download diff file Expand all files Collapse all files

38
examples/dataspaces/software-architecture/manifest.json
View file

@ -65,6 +65,42 @@
"panels": [
"summary",
"relations",
"evidence"
"evidence",
"claims"
],
"schemaVersion": "0.1",
"factPolicy": "show-all",
"relationLabels": {
"adapts": {
"forward": "Adapts",
"inverse": "Adapted by"
},
"uses": {
"forward": "Uses",
"inverse": "Used by"
},
"addressed-by": {
"forward": "Addressed by",
"inverse": "Addresses"
},
"related-to": {
"forward": "Related to",
"inverse": "Related to"
},
"documents": {
"forward": "Documents",
"inverse": "Documented by"
},
"visualizes": {
"forward": "Visualizes",
"inverse": "Visualized by"
},
"affects": {
"forward": "Affects",
"inverse": "Affected by"
}
},
"acyclicPredicates": [
"documents"
]
}

212
examples/dataspaces/software-architecture/snapshot.json
View file

@ -3,7 +3,7 @@
"dataspace": {
"id": "software-architecture",
"title": "Software Architecture",
"description": "A small illustrative collection of patterns and ideas in software design"
"description": "A small illustrative collection of patterns and ideas in software design. The sentences were written for this demo and are not quotations from another corpus."
},
"kinds": [
{
@ -42,108 +42,153 @@
"kindId": "concept",
"title": "Coupling",
"tldr": "The degree to which software elements depend on one another.",
"summary": "The degree to which software elements depend on one another. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "Coupling is how much one software element must know about another in order to work.",
"tags": [
"dependency"
],
"sourceRefs": [
"src:software-architecture:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:coupling:tldr"
]
},
{
"id": "urn:ce:software-architecture:concept:cohesion",
"kindId": "concept",
"title": "Cohesion",
"tldr": "The degree to which a module groups related responsibilities.",
"summary": "The degree to which a module groups related responsibilities. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "Cohesion is how closely the responsibilities inside one module belong together.",
"tags": [
"modularity"
],
"sourceRefs": [
"src:software-architecture:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:cohesion:tldr"
]
},
{
"id": "urn:ce:software-architecture:concept:interface",
"kindId": "concept",
"title": "Interface contract",
"tldr": "An agreed description of interaction between components.",
"summary": "An agreed description of interaction between components. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "An interface contract names the interactions two parts are allowed to rely on.",
"tags": [
"boundary"
],
"sourceRefs": [
"src:software-architecture:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:interface:tldr"
]
},
{
"id": "urn:ce:software-architecture:pattern:adapter",
"kindId": "pattern",
"title": "Adapter pattern",
"tldr": "An adapter translates between interfaces.",
"summary": "An adapter translates between interfaces. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "An adapter lets a caller use one interface while the callee offers another.",
"tags": [
"translation"
],
"sourceRefs": [
"src:software-architecture:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:adapter:tldr"
]
},
{
"id": "urn:ce:software-architecture:pattern:ports-adapters",
"kindId": "pattern",
"title": "Ports and adapters",
"tldr": "A pattern for isolating core logic from outside systems.",
"summary": "A pattern for isolating core logic from outside systems. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "Ports and adapters keep domain logic from importing the details of a database, a UI, or a network.",
"tags": [
"isolation"
],
"sourceRefs": [
"src:software-architecture:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:ports-adapters:tldr"
]
},
{
"id": "urn:ce:software-architecture:pattern:event-driven",
"kindId": "pattern",
"title": "Event-driven architecture",
"tldr": "Software components communicate through events.",
"summary": "Software components communicate through events. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "In an event-driven arrangement, parts announce facts and other parts react, instead of calling each other directly.",
"tags": [
"communication"
],
"sourceRefs": [
"src:software-architecture:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:event-driven:tldr"
]
},
{
"id": "urn:ce:software-architecture:person:alexander",
"kindId": "person",
"title": "Christopher Alexander",
"tldr": "Architect whose pattern-language ideas influenced software design.",
"summary": "Architect whose pattern-language ideas influenced software design. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "Christopher Alexander described pattern languages for buildings. Software designers later borrowed that way of naming recurring forms.",
"tags": [
"patterns"
],
"sourceRefs": [
"src:software-architecture:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:alexander:tldr"
]
},
{
"id": "urn:ce:software-architecture:artifact:adr",
"kindId": "artifact",
"title": "Architecture Decision Record",
"tldr": "A lightweight record of architectural decisions and rationale.",
"summary": "A lightweight record of architectural decisions and rationale. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "An architecture decision record states a decision, its context, and the consequences the writers accepted.",
"tags": [
"record"
],
"sourceRefs": [
"src:software-architecture:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:adr:tldr"
]
},
{
"id": "urn:ce:software-architecture:artifact:c4",
"kindId": "artifact",
"title": "C4 model diagram",
"tldr": "A set of views for communicating software architecture.",
"summary": "A set of views for communicating software architecture. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "The C4 model offers a small set of diagrams, from system context down to code, so different readers can stop at the level they need.",
"tags": [
"diagram"
],
"sourceRefs": [
"src:software-architecture:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:c4:tldr"
]
}
],
"relations": [
@ -210,5 +255,116 @@
"src:software-architecture:authored-demo"
]
}
],
"claims": [
{
"id": "claim:coupling:tldr",
"subjectId": "urn:ce:software-architecture:concept:coupling",
"key": "tldr",
"value": "The degree to which software elements depend on one another.",
"status": "asserted",
"evidenceRefs": [
"src:software-architecture:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:cohesion:tldr",
"subjectId": "urn:ce:software-architecture:concept:cohesion",
"key": "tldr",
"value": "The degree to which a module groups related responsibilities.",
"status": "asserted",
"evidenceRefs": [
"src:software-architecture:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:interface:tldr",
"subjectId": "urn:ce:software-architecture:concept:interface",
"key": "tldr",
"value": "An agreed description of interaction between components.",
"status": "asserted",
"evidenceRefs": [
"src:software-architecture:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:adapter:tldr",
"subjectId": "urn:ce:software-architecture:pattern:adapter",
"key": "tldr",
"value": "An adapter translates between interfaces.",
"status": "asserted",
"evidenceRefs": [
"src:software-architecture:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:ports-adapters:tldr",
"subjectId": "urn:ce:software-architecture:pattern:ports-adapters",
"key": "tldr",
"value": "A pattern for isolating core logic from outside systems.",
"status": "asserted",
"evidenceRefs": [
"src:software-architecture:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:event-driven:tldr",
"subjectId": "urn:ce:software-architecture:pattern:event-driven",
"key": "tldr",
"value": "Software components communicate through events.",
"status": "asserted",
"evidenceRefs": [
"src:software-architecture:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:alexander:tldr",
"subjectId": "urn:ce:software-architecture:person:alexander",
"key": "tldr",
"value": "Architect whose pattern-language ideas influenced software design.",
"status": "asserted",
"evidenceRefs": [
"src:software-architecture:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:adr:tldr",
"subjectId": "urn:ce:software-architecture:artifact:adr",
"key": "tldr",
"value": "A lightweight record of architectural decisions and rationale.",
"status": "asserted",
"evidenceRefs": [
"src:software-architecture:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:c4:tldr",
"subjectId": "urn:ce:software-architecture:artifact:c4",
"key": "tldr",
"value": "A set of views for communicating software architecture.",
"status": "asserted",
"evidenceRefs": [
"src:software-architecture:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:unknown:numeric-scale",
"subjectId": "urn:ce:software-architecture:concept:coupling",
"key": "numeric-scale",
"status": "unknown",
"evidenceRefs": [
"src:software-architecture:authored-demo"
],
"observedAt": "2026-10-12"
}
]
}

43
examples/dataspaces/systems-thinking/manifest.json
View file

@ -65,6 +65,45 @@
"panels": [
"summary",
"relations",
"evidence"
]
"evidence",
"claims"
],
"schemaVersion": "0.1",
"factPolicy": "show-all",
"relationLabels": {
"represented-by": {
"forward": "Represented by",
"inverse": "Represents"
},
"scopes": {
"forward": "Scopes",
"inverse": "Scoped by"
},
"associated-with": {
"forward": "Associated with",
"inverse": "Associated with"
},
"authored-by": {
"forward": "Authored by",
"inverse": "Authored"
},
"related-to": {
"forward": "Related to",
"inverse": "Related to"
},
"models": {
"forward": "Models",
"inverse": "Modeled by"
},
"explores": {
"forward": "Explores",
"inverse": "Explored by"
}
},
"acyclicPredicates": [
"authored-by"
],
"theme": {
"accent": "indigo"
}
}

212
examples/dataspaces/systems-thinking/snapshot.json
View file

@ -3,7 +3,7 @@
"dataspace": {
"id": "systems-thinking",
"title": "Systems Thinking",
"description": "A small illustrative collection of ideas in systems theory"
"description": "A small illustrative collection of ideas in systems theory. The sentences were written for this demo and are not quotations from another corpus."
},
"kinds": [
{
@ -42,108 +42,153 @@
"kindId": "concept",
"title": "Feedback",
"tldr": "Effects of actions change subsequent behavior.",
"summary": "Effects of actions change subsequent behavior. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "A feedback loop sends the result of an action back so the next action can change.",
"tags": [
"regulation"
],
"sourceRefs": [
"src:systems-thinking:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:feedback:tldr"
]
},
{
"id": "urn:ce:systems-thinking:concept:emergence",
"kindId": "concept",
"title": "Emergence",
"tldr": "Collective behavior arises through interactions.",
"summary": "Collective behavior arises through interactions. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "Emergence is behavior of a whole that is not obvious from one part looked at alone.",
"tags": [
"structure"
],
"sourceRefs": [
"src:systems-thinking:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:emergence:tldr"
]
},
{
"id": "urn:ce:systems-thinking:concept:variety",
"kindId": "concept",
"title": "Requisite variety",
"tldr": "Effective regulation requires sufficient response variety.",
"summary": "Effective regulation requires sufficient response variety. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "Requisite variety says a regulator needs enough responses to match the situations it faces.",
"tags": [
"regulation"
],
"sourceRefs": [
"src:systems-thinking:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:variety:tldr"
]
},
{
"id": "urn:ce:systems-thinking:concept:system-boundary",
"kindId": "concept",
"title": "System boundary",
"tldr": "A distinction determines what is examined as a system.",
"summary": "A distinction determines what is examined as a system. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "A system boundary is the distinction that decides which interactions count as inside the system.",
"tags": [
"boundary"
],
"sourceRefs": [
"src:systems-thinking:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:system-boundary:tldr"
]
},
{
"id": "urn:ce:systems-thinking:person:ashby",
"kindId": "person",
"title": "W. Ross Ashby",
"tldr": "Cybernetics researcher associated with requisite variety.",
"summary": "Cybernetics researcher associated with requisite variety. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "W. Ross Ashby wrote about regulation and variety in mid-century cybernetics.",
"tags": [
"cybernetics"
],
"sourceRefs": [
"src:systems-thinking:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:ashby:tldr"
]
},
{
"id": "urn:ce:systems-thinking:person:meadows",
"kindId": "person",
"title": "Donella Meadows",
"tldr": "Systems thinker known for work on leverage points.",
"summary": "Systems thinker known for work on leverage points. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "Donella Meadows described places in a system where a small change can have a large effect.",
"tags": [
"leverage"
],
"sourceRefs": [
"src:systems-thinking:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:meadows:tldr"
]
},
{
"id": "urn:ce:systems-thinking:publication:thinking-in-systems",
"kindId": "publication",
"title": "Thinking in Systems",
"tldr": "A widely read introductory systems-thinking book.",
"summary": "A widely read introductory systems-thinking book. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "Thinking in Systems is an introductory book that explains stocks, flows, and feedback with everyday examples.",
"tags": [
"introduction"
],
"sourceRefs": [
"src:systems-thinking:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:thinking-in-systems:tldr"
]
},
{
"id": "urn:ce:systems-thinking:method:causal-loop",
"kindId": "method",
"title": "Causal loop diagram",
"tldr": "A diagram representing causal influences and feedback.",
"summary": "A diagram representing causal influences and feedback. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "A causal loop diagram draws influence arrows and marks whether each link reinforces or balances.",
"tags": [
"diagram"
],
"sourceRefs": [
"src:systems-thinking:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:causal-loop:tldr"
]
},
{
"id": "urn:ce:systems-thinking:method:stock-flow",
"kindId": "method",
"title": "Stock and flow model",
"tldr": "A representation of accumulations and their rates of change.",
"summary": "A representation of accumulations and their rates of change. This fixture is illustrative and does not constitute a sourced scholarly claim.",
"tags": [],
"summary": "A stock and flow model separates accumulations from the rates that fill or drain them.",
"tags": [
"diagram"
],
"sourceRefs": [
"src:systems-thinking:authored-demo"
],
"asOf": "2026-10-12"
"asOf": "2026-10-12",
"claimRefs": [
"claim:stock-flow:tldr"
]
}
],
"relations": [
@ -210,5 +255,116 @@
"src:systems-thinking:authored-demo"
]
}
],
"claims": [
{
"id": "claim:feedback:tldr",
"subjectId": "urn:ce:systems-thinking:concept:feedback",
"key": "tldr",
"value": "Effects of actions change subsequent behavior.",
"status": "asserted",
"evidenceRefs": [
"src:systems-thinking:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:emergence:tldr",
"subjectId": "urn:ce:systems-thinking:concept:emergence",
"key": "tldr",
"value": "Collective behavior arises through interactions.",
"status": "asserted",
"evidenceRefs": [
"src:systems-thinking:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:variety:tldr",
"subjectId": "urn:ce:systems-thinking:concept:variety",
"key": "tldr",
"value": "Effective regulation requires sufficient response variety.",
"status": "asserted",
"evidenceRefs": [
"src:systems-thinking:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:system-boundary:tldr",
"subjectId": "urn:ce:systems-thinking:concept:system-boundary",
"key": "tldr",
"value": "A distinction determines what is examined as a system.",
"status": "asserted",
"evidenceRefs": [
"src:systems-thinking:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:ashby:tldr",
"subjectId": "urn:ce:systems-thinking:person:ashby",
"key": "tldr",
"value": "Cybernetics researcher associated with requisite variety.",
"status": "asserted",
"evidenceRefs": [
"src:systems-thinking:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:meadows:tldr",
"subjectId": "urn:ce:systems-thinking:person:meadows",
"key": "tldr",
"value": "Systems thinker known for work on leverage points.",
"status": "asserted",
"evidenceRefs": [
"src:systems-thinking:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:thinking-in-systems:tldr",
"subjectId": "urn:ce:systems-thinking:publication:thinking-in-systems",
"key": "tldr",
"value": "A widely read introductory systems-thinking book.",
"status": "asserted",
"evidenceRefs": [
"src:systems-thinking:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:causal-loop:tldr",
"subjectId": "urn:ce:systems-thinking:method:causal-loop",
"key": "tldr",
"value": "A diagram representing causal influences and feedback.",
"status": "asserted",
"evidenceRefs": [
"src:systems-thinking:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:stock-flow:tldr",
"subjectId": "urn:ce:systems-thinking:method:stock-flow",
"key": "tldr",
"value": "A representation of accumulations and their rates of change.",
"status": "asserted",
"evidenceRefs": [
"src:systems-thinking:authored-demo"
],
"observedAt": "2026-10-12"
},
{
"id": "claim:unknown:formal-measure",
"subjectId": "urn:ce:systems-thinking:concept:system-boundary",
"key": "formal-measure",
"status": "unknown",
"evidenceRefs": [
"src:systems-thinking:authored-demo"
],
"observedAt": "2026-10-12"
}
]
}