andreibesleaga/agentic-system-core

A specification for publishing machine-discoverable knowledge bundles — the Agentic Knowledge Web.
What this repository holds is the specification itself — numbered normative rules, three JSON Schemas, an OWL 2 RL ontology and a suite of conformance test vectors — together with the reference engine that implements it, its command line agsc, and the nine independent checkers of AGSC-09-90 — seven validators and two generators — that anyone can run against any distribution of the format (the repository also holds the maintainer's own tools, which do not ship).
## Status
Released. This tree states specification 1.0.0. spec/00-overview.md is authoritative, and it is the file to read rather than this line. The packages — agentic-system-core and its short alias agsc-cli on npm, and agentic-system-core on PyPI — carry version 1.0.1 (see "Versions" below) and are published from the package tag; the name-reservation placeholders that preceded them shipped no runtime and are marked deprecated on npm and yanked on PyPI. Install with npm install agentic-system-core, or pip install agentic-system-core. The reference engine claims Level 3 (its claim).
Versions. Two numbers, stated apart. The specification version (specversion,
declared in spec/00-overview.md) names the rules, schemas, vocabulary and conformance
vectors; a Bundle declares it in agsc.config.json. The package version (package.json,
agentic-system-core and agsc-cli on npm, agentic-system-core on PyPI) names the
implementation; it moves alone for a patch that changes no rule and no emitted byte —
a dependency fix, a defect in a check — and a package-only release carries the package
tag v and no specification tag. agsc --version prints the package version;
the conformance claim names both ("agentic-system-core 1.0.1 conforms to
AgenticSystemCore 1.0.0, Level 3"); the change log says for every release whether the
specification moved.
The specification's own site is AgenticSystemCore.com.
## In three sentences
A Bundle is a folder of Markdown files with a small block of typed fields at the
top of each; the specification says how that folder becomes a knowledge node — a
static website plus a graph, a search index, text files for agents and a discovery
document — with the same bytes from any implementation. People and agents read a node
through ordinary web addresses, change it only by proposals that a person ratifies, and
compose its items into a starting harness — files an architect or an agent runtime
starts from. Nodes find and cite each other with no server in between.
## What is different about it
To the author's knowledge, no other system combines discovery through already-registered web
mechanisms with an integrity digest on every artefact link of its discovery document, a typed graph with a
published ontology, machine artefacts whose bytes are fixed by expected-byte
conformance vectors, governance in which every change — human or agent — arrives as a
proposal carrying its provenance and a person ratifies it (directly, or by a standing
rule a person recorded in the node's configuration), and composition of the same files
into a starting harness, with no server required at any point.