ad-hoc-semantic-reconciliation

The results — a completed four-scenario study

The empirical realisation of the research programme in ad hoc semantic reconciliation. Four operational scenarios, built, run against a validated gold standard, and reported, with a master report drawing them into one synthesis.

Part of the larger project — the theory and programme that motivate this study are in ../proposal/; the interactive demonstrations are in ../demos/.

The central finding, established across all four scenarios: it is cognition that completes a reconciliation. Descriptor methods — matching names, then names plus a gloss — carry it to a ceiling and stop, historically leaving the rest to a standard or a person. Where both systems can reason, the remainder is closed autonomously, with no model agreed in advance and no human in the loop, and only as cognition recedes does a residual have to be referred onward. A thin, published reference can substitute for cognition, or supply an inert side the facts it lacks — but its reach ends there: it hands over information, never the authority to decide, whose value governs or whether a trade-off is acceptable. And the pragmatic layer — what a reconciled thing is for, whether it matters, who decides — is the frontier the descriptor methods never reach: decisive for meaning, and itself bounded by the agent’s capability.

Start here — the master report

reports/MASTER_REPORT.md  ·  PDF  ·  slides (PDF)  ·  slides (PPTX) — the synthesis that sits atop the four scenarios. It introduces the idea once (the lift, portable semantic models, the family of reconciliation operations, and the cognition spectrum), distils each scenario to its essentials, and then gathers the findings so they can be read as one result: what works and how far, the six theses the scenarios establish, the evidence behind them along a set of cross-cutting readings (cognitive load, model power, the reference, placement and failure, reach, the pragmatic layer, and what it takes to produce the inputs the whole thing runs on), two tables mapping every finding to its placement and to the process stage it acts on, the surprises, and the scope. The slide deck carries the same synthesis for readers who prefer slides.

The lift — a data model becomes a portable, self-describing semantic model.

Reconciliation over two lifted models — grounded correspondences bound through a thin reference, a rejected cognate, and what is honestly left unbound (no counterpart, or the residual referred onward).

The Internet-Draft (IETF NMRG)

HTML  ·  PDF  ·  TXT  ·  XML — draft-janz-nmrg-adhoc-semantic-reconciliation, the Internet-Draft that condenses this work for the IETF Network Management Research Group (NMRG): the lift and portable semantic models, the family of reconciliation operations, the taxonomy of where models diverge (including the one-to-zero true gap), the placement of cognition, and what a next step on a live operator system would involve. The XML is the xml2rfc source; the HTML, PDF, and TXT are its renderings.

The four scenarios

Each scenario takes the same frame to a new operation. Each has a report (renders inline), a print-ready PDF, and an interactive demo (opens in your browser; see ../demos/ for download links too).

1/4 · Configuration  ·  PDF  ·  ▶ demo — two standard models of one network. ONF TAPI ↔ IETF TEAS/ACTN, seeded with false cognates and opaque items. The founding scenario: it shows the thin reference substituting for cognition, the benefit capability-dependent, verification catching the traps, and work scaling linearly with a reference against quadratically without. Its four sub-studies are folded into the report and preserved as method notes under notes/studies/.

2/4 · Intent  ·  PDF  ·  ▶ demo — refinement, negotiation, and a service that renegotiates itself. A customer’s intent reconciled against an operator’s catalogue by refinement, not equivalence; verification becomes a satisfaction check; a negotiation appears; the pragmatic operation enters as a portable movable policy; and the exchange recurs across a service’s life. Grounded in the IRTF NMRG draft draft-janz-nmrg-naas-agentic-negotiation.

3/4 · Standard-free  ·  PDF  ·  ▶ demo — reconciling with no public standard. Two home-grown, private models meet at one seam. The central result is a mirror: without the constructed reference the strong agent under-commits (defers at perfect precision) and the weak agent mis-commits (binds wrongly). A single descriptive field unlocks a capable agent; a bare shared pointer is worse than nothing. Building the shared ground is the work — and, run end to end, an agent that builds it itself lifts from 0.20 to 0.80 (0.90 with a decisive virtual experiment).

4/4 · Observability  ·  PDF  ·  ▶ demo — an alarm is not an anomaly. A legacy fault manager and an IETF NMOP agent (RFC 9940) reconcile two observability worlds, carrying the programme’s deepest false cognate and a one-to-many decomposition. The pragmatics carry the operative verdict — but only for an agent able to carry them; while correlation, a structural pragmatic, is robust across the whole ladder.

The reconciling agents are one model ladder for the whole study: gpt-5.6-sol (strong), gpt-5-mini (mid), gpt-5-nano (weak) — “sol / mini / nano” — chosen so the ladder isolates model strength rather than provider or architecture.

How it works

The lift is the move from a data model (a schema and its records: already a partial semantic picture, but a fixed one, with much of its meaning left implicit) to a semantic model that carries its meaning explicitly. A semantic model has three parts: an ontology, including its lexicon, with a schematic layer (concepts, their kinds and relations, and the labels and synonyms that name them: the TBox) and a concrete layer (the instances that populate them: the ABox); pragmatics, the contextual information a consumer needs (what a thing is for, whose authority governs it, in what context it holds), obtained not by lookup but by judgement; and provenance (who asserted each part, by what method, how firmly). The lift itself is a cognitive act, aided by supports that are not parts of the model: definitions, worked examples, a canonical example, and an optional link to a shared reference. Being self-describing, a lifted model is portable: any cognitive consumer can pick it up with no pre-agreed standard. Reconciliation runs over these lifted models, not over labels.

Drawn out, the ontology and its instances are a knowledge graph: the schematic layer is its schema (typed concepts and permitted relations) and the concrete layer is its assertions (typed individuals and the edges among them). Reconciliation divides the same way — aligning concepts is ontology matching, and co-referencing individuals is entity resolution over the graph — which is where the community’s knowledge-graph work for network operations meets this approach. The pragmatics and provenance are what the semantic model adds beyond a bare graph, and they are exactly what a thin reference cannot supply.

A case is two lifted semantic models plus a gold standard derived from the models and validated, so it cannot drift. A reasoning stack reconciles them — deterministic controls and a language-model agent run at each point on the cognition spectrum (both live, one inert, both inert). At the fully-cognitive end the two live sides reconcile as two separate agents under information asymmetry, each holding only its own lifted model and a surface catalogue of the other’s, proposing correspondences and ratifying the other’s, with the option of a decisive virtual experiment to settle a hard pair; as a side goes inert a single agent reconstructs it. The harness scores the output against the gold and records quality — precision, resolved fraction, surviving false cognates, and the residual — and, for the agent, cognitive effort (reasoning tokens, latency). A resolved fraction below one is deferral, not error: the residual is the shortfall from full cognition’s reach, and it grows as cognition recedes.

What’s new (2026-09-27)

A second review pass over the master report, the addition of the IETF Internet-Draft to this repository, and an editable PPTX of the deck. The findings, theses, and results are unchanged; the report changes add one missing case to the account of divergence and tighten naming, framing, and two captions.

What’s new (2026-09-24)

A review pass over the master report and the deck, responding to detailed feedback. The findings, theses, and results are unchanged; the changes tighten a few headline claims, add transparency, and bring the deck up to date with the recent conceptual work (2026-09-22).

What’s new (2026-09-22)

A conceptual sharpening of the master report, and a new experimental direction, drawn from a working exchange on how the lift actually works. The findings, theses, and results are unchanged; what is added is a clearer account of how the lift produces meaning and what would prove it on real systems. A companion synopsis of related work is added under reports/.

What’s new (2026-09-20)

A small wording pass on the master report, sharpening three phrasings. The findings, theses, and structure are unchanged; only the prose is tightened.

The master report PDF is rebuilt to match.

What’s new (2026-09-17)

Mostly a reframing of the whole account, together with the portability experiments the reframing rests on. The findings are unchanged; what changed is the frame around them, the evidence under one half of it, and the deck.

The master report and the four sub-reports are rebuilt to match. The portability drivers, results, and figures live under pipeline/, results/, and figures/.

What’s new (2026-09-15)

A focused programme drilling into the one question the four-scenario study leaves open at its own boundary: whether the semantic and pragmatic inputs a reconciliation runs on can be produced from the thin, real interface models a deployment actually meets — careless YANG, or REST whose data is present but whose meaning is implicit in the application — without becoming a heavy design-time process. Five experiments (E16–E20) settle a position, drawn together in a standalone note:

reports/NOTE_producing_the_inputs.md — Producing the inputs: a three-route decision for thin sources.

The position, in one line: producing the inputs is a route decision — lift, governed overlay, or live elicitation, selected by whether the source is inert or cognitive — and the governed overlay is the robust, capability-independent route, with the design-time burden bounded and, on this evidence, small. What the experiments establish:

New drivers under pipeline/ (inert_vs_cognitive, cold_start_lift, minimum_overlay, design_run_split, with figure scripts), a new REST case config_rest built from the two real specifications, and results and figures under results/ and figures/.

What’s new (2026-09-14)

This revision extends the study at the experimental end with a substantial programme of further experiments, biting into the harder half of the problem — producing and aligning the inputs, not only reconciling models that already share a reference — and replicating the sharp findings across additional model families. The central findings are unchanged and deepened: the new results are woven into the master report’s synthesis (including a reading on producing the inputs, §13.10), and each scenario report gains a Further experiments section (report 1/4 §5, report 2/4 §5, report 3/4 §6, report 4/4 §5).

What’s new (2026-09-10)

This revision brings the pragmatic layer to the front, shows the lift itself as an act of cognition, and makes the agent-performed lift replicable from the command line. The central findings are unchanged; the reports carry the results in place.

What’s new (2026-09-08)

This revision deepens the fully-cognitive end and adds two controls. As before, the central findings are unchanged and the reports carry the results in place; this note is for readers tracking what moved.

What’s new (2026-09-05)

This revision strengthens the study in-house — the central findings are unchanged and hold — and closes the in-house gaps the first cut left open, leaving only the genuinely external one (real network data). The reports carry the results in place; this summary is here for readers tracking what moved between revisions.

What remains is now genuinely external: larger and more varied cases drawn from real networks, and the real-data grounding that only carrier and standards-body collaboration can supply. The breadth cases above are still authored by the same hand, so they test robustness to variation, not to real data — which is exactly the gap that external collaboration exists to close.

Repository layout (study/)

reports/                      the deliverables
    MASTER_REPORT.md              the synthesis — start here
    REPORT_1of4_configuration.md  scenario 1 · configuration (TAPI ↔ TEAS)
    REPORT_2of4_intent.md         scenario 2 · intent (refinement, negotiation, lifecycle)
    REPORT_3of4_standard_free.md  scenario 3 · standard-free (no standard)
    REPORT_4of4_observability.md  scenario 4 · observability (alarm ≠ anomaly)
notes/
    studies/                  scenario-1 method notes (lift baseline, reference anatomy,
                              instance disambiguation, verification modes)
    design/                   design notes of record, per scenario
    archive/                  superseded working notes
    SETUP_OPENAI.md           how to supply the API key (kept out of the repo)
figures/                      all report figures (regenerated by pipeline/figures*.py)
src/reconcile/                the harness: models, reference, metrics, stacks, oracles
benchmark/                    case builders and cases/ (two lifted models, reference, traps, gold)
results/                      the exact per-run data behind every figure and table
pipeline/                     all runner, figure, and build scripts
tests/                        offline tests of the stacks and scoring (no API)
pyproject.toml

Quick start

Run from the study/ directory. The controls, gold derivations, offline tests, figures, and PDF build need no model access (standard-library Python plus matplotlib/markdown/wkhtmltopdf). The language-model runs need openai and an API key — see notes/SETUP_OPENAI.md — and reach api.openai.com, so they run where that is available.

cd study

# deterministic, no API:
python pipeline/run.py --case config_big_hard --no-write     # controls only
python pipeline/scaling.py --max-n 12                         # the scaling result
python -m pytest tests/                                       # offline tests
python pipeline/figures_master.py                             # regenerate the master figures
python pipeline/build_pdfs.py                                 # rebuild every report PDF

# the language-model studies (need OpenAI; run where api.openai.com is reachable):
python pipeline/run.py --case config_big_hard --agent --trials 4 \
  --placement both_cognitive,one_inert,both_inert \
  --model gpt-5.6-sol,gpt-5-mini,gpt-5-nano
python pipeline/intent_study.py     --model gpt-5.6-sol,gpt-5-mini,gpt-5-nano
python pipeline/pragmatics_study.py --model gpt-5.6-sol,gpt-5-mini,gpt-5-nano
python pipeline/observability_study.py --model gpt-5.6-sol,gpt-5-mini,gpt-5-nano

# the agent-performed lift, on its own, across every schema case (dumps each lifted model to JSON;
# add --trace to record the agent's stated evidence per concept):
python pipeline/lift_study.py --lift-only --cases all --model gpt-5.6-sol,gpt-5-mini,gpt-5-nano

Per-scenario run commands are in each report’s Reproducibility section, and the method notes under notes/studies/ carry the sub-study commands.

Grounding and scope

The study operationalizes and empirically tests the claims of the proposal: the IRTF NMRG work on agentic network-as-a-service negotiation, the cross-domain provisioning demonstration, and the IETF NMOP anomaly/alarm model (RFC 9940). The claims are existential and mechanistic — this is how ad hoc reconciliation works, and here it is working — established on single, seeded cases built to exercise each mechanism and prove each trap, across the model ladder; they are not population estimates. What remains is now external: larger and more varied cases drawn from real networks, and the real-data grounding that only carrier and standards-body collaboration can supply.

Choose a license before publishing.