Skip to content

Add Knowledge Unit schema (IETF draft-farley-acta-knowledge-units)#5529

Open
tomjwxf wants to merge 2 commits intoSchemaStore:masterfrom
tomjwxf:add-knowledge-unit-schema
Open

Add Knowledge Unit schema (IETF draft-farley-acta-knowledge-units)#5529
tomjwxf wants to merge 2 commits intoSchemaStore:masterfrom
tomjwxf:add-knowledge-unit-schema

Conversation

@tomjwxf
Copy link
Copy Markdown

@tomjwxf tomjwxf commented Apr 6, 2026

Summary

Adds the Knowledge Unit JSON Schema, defined by IETF Internet-Draft draft-farley-acta-knowledge-units-00.

Knowledge Units are verified knowledge artifacts produced through structured multi-model deliberation. The format captures:

  • Structured consensus (agreed/disputed/uncertain claims with per-model positions)
  • Source provenance (content hashes for freshness validation)
  • Lifecycle management (active/stale/superseded with typed operations)
  • Cryptographic receipt binding (Ed25519 signatures per deliberation round)
  • Inter-KU relations (supports/contradicts/refines/extends/depends_on)

File matches

  • ku-*.json
  • knowledge-unit.json
  • **/ku/*.json

Schema source

Tests

  • valid-minimal.json - Required fields only
  • valid-full.json - All fields including disputed claims, sources, relations

Knowledge Units are verified knowledge artifacts produced through
structured multi-model deliberation. The format captures consensus
(agreed/disputed/uncertain), provenance (models, sources with content
hashes), lifecycle (active/stale/superseded), and cryptographic receipt
binding (Ed25519).

Specification: IETF Internet-Draft draft-farley-acta-knowledge-units-00
Reference implementation: https://acta.today/wiki
Schema source: https://github.com/VeritasActa/drafts

File matches: ku-*.json, knowledge-unit.json, **/ku/*.json
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 6, 2026

Thanks for the PR!

This section of the codebase is owned by @madskristensen and @hyperupcall - if they write a comment saying "LGTM" then it will be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants