Skip to content

Commit c240229

Browse files
docs(machine_readable): ochrance-framework checkpoint — refresh 6a2 + ANCHOR (#18)
$(cat <<'EOF' ## Summary - Replaces the March 2026 thin `.scm`-converted stubs in `.machine_readable/6a2/` and `anchors/ANCHOR.a2ml` with a full machine-readable checkpoint reflecting ochrance-framework's actual current role and status as of 2026-06-05. - Records decision D1 throughout: this repo's duplicate `ochrance-core` is retired; canonical proofs and production code live in the `ochrance` repo. The framework's genuinely novel contribution — the mode-indexed, subsystem-parameterised `VerifiedSubsystem` interface — has been harvested into `ochrance`. This repo retains its real value: architecture, A2ML spec, FFI contract, threat model, whitepaper, L4 policies, and roadmap. - ANCHOR gets a 2026-06-05 realignment record for D1, citing `docs/ARCHITECTURE.md` as authority. ### Per-file changes | File | What changed | |---|---| | `STATE.a2ml` | phase → `maintenance`; completion 5% → 65%; `what-this-repo-owns` / `retired` sections; honest blockers; recent CI merge history | | `META.a2ml` | D1 listed first in decisions; ADR-001–005 condensed to flat list; ochrance-style `architecture` block | | `NEUROSYM.a2ml` | obligations split into `defined-here` / `discharged-in-ochrance` / `open`; `honest-bounds` note; compact symbolic-rules list | | `ECOSYSTEM.a2ml` | reoriented as architecture+docs repo; ochrance listed first as canonical core; svalinn, valence-shell, boj-server, verisimdb added | | `AGENTIC.a2ml` | D1 `core-authority` guard added; trimmed to ochrance-exemplar conciseness; retains FFI security boundary | | `PLAYBOOK.a2ml` | build split into this-repo (stubs) and canonical-core (ochrance per D1); aligned with Justfile recipes | | `ANCHOR.a2ml` | 2026-06-05 realignment record for D1 core-retirement + framework role-clarification | ## Test plan - [ ] Confirm all seven files have correct SPDX header (`MPL-2.0`) and copyright line - [ ] Confirm ANCHOR realignment record date is `2026-06-05` and authority is `docs/ARCHITECTURE.md` - [ ] Confirm no Idris source, contractiles/, svc/, integrations/, or other files were touched - [ ] CI green (RSR antipattern check, SPDX check, workflow linters) https://claude.ai/code/session_011z2t8zAxfcCNLJzU7YdpBQ EOF ) --- _Generated by [Claude Code](https://claude.ai/code/session_011z2t8zAxfcCNLJzU7YdpBQ)_ Co-authored-by: Claude <noreply@anthropic.com>
1 parent c7befcc commit c240229

7 files changed

Lines changed: 221 additions & 638 deletions

File tree

.machine_readable/6a2/AGENTIC.a2ml

Lines changed: 24 additions & 79 deletions
Original file line numberDiff line numberDiff line change
@@ -1,92 +1,37 @@
11
# SPDX-License-Identifier: MPL-2.0
22
# Copyright (c) 2026 Jonathan D.A. Jewell (hyperpolymath) <j.d.a.jewell@open.ac.uk>
33
#
4-
# AGENTIC.a2ml — AI agent constraints and capabilities for Ochrance Framework
4+
# AGENTIC.a2ml — AI agent constraints and capabilities
55
# Defines what AI agents can and cannot do in this repository.
6-
76
[metadata]
87
version = "0.1.0"
9-
last-updated = "2026-02-19"
8+
last-updated = "2026-06-05"
109

1110
[agent-permissions]
12-
can-edit-source = true
13-
can-edit-tests = true
1411
can-edit-docs = true
1512
can-edit-config = true
13+
can-edit-machine-readable = true
14+
can-edit-source = true # Idris2 stubs; proof changes require human review
15+
can-edit-tests = true
1616
can-create-files = true
17-
can-edit-proofs = false # Idris2 proofs must be human-reviewed before merge
18-
can-edit-ffi = false # C FFI shims require manual security review
17+
can-edit-ffi = false # C NVMe shims are attack surface; require manual security review
1918

2019
[agent-constraints]
21-
# What AI agents must NOT do in this repository:
22-
constraints = [
23-
"Never use believe_me in Idris2 code (banned unsafe pattern)",
24-
"Never use assert_total in Idris2 code (banned unsafe pattern)",
25-
"Never use assert_smaller in Idris2 code (banned unsafe pattern)",
26-
"Never use unsafePerformIO in Idris2 code (banned unsafe pattern)",
27-
"Never introduce unsafe{} blocks in Rust code without SAFETY comments",
28-
"Never commit secrets or credentials",
29-
"Never use banned languages (TypeScript, Python, Go, etc.)",
30-
"Never place state files in repository root (must be in .machine_readable/)",
31-
"Never use AGPL license (use MPL-2.0)",
32-
"Never weaken StrictnessLevel (do not change Attested to Checked or Lax)",
33-
"Never bypass proof obligations with postulates or Admitted-equivalent",
34-
"Never modify C FFI shims without flagging for security review",
35-
]
36-
37-
[agents]
38-
# AI agents that interact with this repository
39-
40-
[agents.claude]
41-
role = "primary-development"
42-
model = "claude-opus-4-6"
43-
capabilities = [
44-
"Code generation (Idris2, Rust, C, Julia)",
45-
"Architecture design and ADR drafting",
46-
"Documentation and specification writing",
47-
"Test scaffolding and property specification",
48-
"CI/CD workflow configuration",
49-
"RSR compliance enforcement",
50-
]
51-
limitations = [
52-
"Cannot verify Idris2 totality (requires idris2 compiler)",
53-
"Cannot run proof obligations (requires Echidna dispatch)",
54-
"Cannot deploy to OSTree (requires system access)",
55-
]
56-
57-
[agents.echidna]
58-
role = "proof-synthesis"
59-
type = "neurosymbolic-prover"
60-
capabilities = [
61-
"Neural proof synthesis for Idris2 tactics",
62-
"Cross-prover verification of proof obligations",
63-
"Confidence scoring via 5-level trust hierarchy",
64-
"Portfolio solving across 30 prover backends",
65-
]
66-
interaction = "Ochrance dispatches proof obligations via structured format; Echidna returns synthesised proofs with confidence metadata"
67-
68-
[agents.hypatia]
69-
role = "ci-intelligence"
70-
type = "neurosymbolic-cicd"
71-
capabilities = [
72-
"Pattern detection in verification reports",
73-
"Fleet dispatch to gitbot-fleet bots",
74-
"VeriSimDB integration for weakness tracking",
75-
]
76-
interaction = "Hypatia scans Ochrance on commit; emits Logtalk facts for downstream analysis"
77-
78-
[automation-hooks]
79-
on-enter = "Read 0-AI-MANIFEST.a2ml, then .machine_readable/STATE.a2ml"
80-
on-exit = "Update .machine_readable/STATE.a2ml with session outcomes"
81-
on-commit = "Run just validate-rsr"
82-
on-proof-change = "Flag for human review; do not auto-merge proof modifications"
83-
on-ffi-change = "Flag for security review; C shims must be manually audited"
84-
85-
[review-gates]
86-
# Changes that require human approval before merge
87-
gates = [
88-
{ path = "ochrance-core/src/**/*.idr", gate = "proof-review", reason = "Core Idris2 proofs must be human-verified" },
89-
{ path = "ffi/**/*.c", gate = "security-review", reason = "C FFI shims are attack surface" },
90-
{ path = "modules/*/src/**/*.idr", gate = "proof-review", reason = "Module proofs must be human-verified" },
91-
{ path = ".machine_readable/**", gate = "metadata-review", reason = "SCM file changes affect all agents" },
92-
]
20+
# What AI agents must NOT do:
21+
# - Never use banned proof escapes (believe_me, assert_total, assert_smaller, postulate, unsafePerformIO)
22+
# - Never weaken %default total, nor introduce covering / partial on verification code
23+
# - Never commit secrets or credentials
24+
# - Never use banned languages (TypeScript, Python, Go, etc.)
25+
# - Never place state/meta files in repository root (must live under .machine_readable/)
26+
# - Never use AGPL (license is MPL-2.0)
27+
# - Never modify C FFI shims without flagging for security review
28+
# - Never make proof changes in ochrance-core/ here without noting D1: the canonical source is ochrance
29+
30+
[agent-workflow]
31+
role = "primary surface is docs/ and .machine_readable/; Idris2 stubs for interface reference only"
32+
core-authority = "D1: proof and code changes go to the ochrance repo, not here"
33+
docs-gate = "docs/ changes are the primary maintenance path; keep specs in sync with ochrance implementation"
34+
verification-gate = "idris2 --build ochrance.ipkg must stay clean (stubs only; no new proofs here)"
35+
model-guidance = "Sonnet for docs, architecture, spec writing; Opus for any proof-adjacent reasoning"
36+
on-enter = "Read .machine_readable/6a2/STATE.a2ml; check D1 status before touching ochrance-core/"
37+
on-exit = "Update .machine_readable/6a2/STATE.a2ml with session outcomes if substantive"
Lines changed: 23 additions & 117 deletions
Original file line numberDiff line numberDiff line change
@@ -1,127 +1,33 @@
11
# SPDX-License-Identifier: MPL-2.0
22
# Copyright (c) 2026 Jonathan D.A. Jewell (hyperpolymath) <j.d.a.jewell@open.ac.uk>
33
#
4-
# ECOSYSTEM.a2ml — Project ecosystem position for Ochrance Framework
5-
# Relationships, dependencies, integration points.
6-
4+
# ECOSYSTEM.a2ml — Ecosystem position
75
[metadata]
8-
version = "0.1.0"
9-
last-updated = "2026-02-19"
10-
11-
[project]
12-
name = "Ochrance Framework"
13-
purpose = "Modular verification framework for subsystem integrity using dependent types (Idris2)"
14-
role = "verification-framework" # e.g. ffi-infrastructure, cli-tool, library, service
6+
project = "ochrance-framework"
7+
ecosystem = "hyperpolymath"
8+
last-updated = "2026-06-05"
159

16-
[position-in-ecosystem]
17-
tier = "infrastructure" # 1 | 2 | infrastructure
18-
description = """
19-
Ochrance sits at the infrastructure tier of the hyperpolymath verification stack.
20-
It provides the formal verification layer for operating system subsystem integrity,
21-
bridging the gap between dependent-type theory (Idris2) and practical system
22-
deployment (OSTree/Fedora Kinoite). It consumes Echidna for neural proof synthesis
23-
and feeds verification results to Hypatia for CI/CD intelligence.
24-
"""
10+
[position]
11+
type = "architecture + documentation"
12+
role = """Architecture, specification, and documentation repository for the Ochránce neurosymbolic verification system. Defines the L0–L5 trust pyramid, A2ML specification, FFI contract, threat model, whitepaper, L4 policies, and roadmap. The duplicate core has been retired (D1); canonical proofs and production code live in the ochrance repo."""
2513

2614
[related-projects]
27-
# relationship types: sibling-standard, dependency, dependent, inspiration, potential-consumer
28-
29-
[[related-projects.project]]
30-
name = "echidna"
31-
relationship = "sibling"
32-
description = "Neurosymbolic theorem proving platform with 30 prover backends"
33-
interaction = "Ochrance dispatches proof obligations to Echidna; Echidna synthesises Idris2 proofs via neural tactics"
34-
url = "https://github.com/hyperpolymath/echidna"
35-
36-
[[related-projects.project]]
37-
name = "verisimdb"
38-
relationship = "sibling"
39-
description = "Verisimilitude Database for vulnerability and weakness tracking"
40-
interaction = "Ochrance scan results feed into VeriSimDB for cross-repo weakness aggregation"
41-
url = "https://github.com/hyperpolymath/verisimdb"
42-
43-
[[related-projects.project]]
44-
name = "panic-attacker"
45-
relationship = "sibling"
46-
description = "Security weakness scanner (panic-attack CLI)"
47-
interaction = "Runs security scans against Ochrance codebase; results ingested by VeriSimDB"
48-
url = "https://github.com/hyperpolymath/panic-attacker"
49-
50-
[[related-projects.project]]
51-
name = "hypatia"
52-
relationship = "potential-consumer"
53-
description = "Neurosymbolic CI/CD intelligence platform"
54-
interaction = "Consumes Ochrance verification reports for CI pipeline intelligence and pattern detection"
55-
url = "https://github.com/hyperpolymath/hypatia"
56-
57-
[[related-projects.project]]
58-
name = "eclexia"
59-
relationship = "sibling"
60-
description = "Programming language with formal verification, shadow pricing, carbon-aware scheduling"
61-
interaction = "Shares formal verification infrastructure; potential mutual backend integration"
62-
url = "https://github.com/hyperpolymath/eclexia"
63-
64-
[[related-projects.project]]
65-
name = "gitbot-fleet"
66-
relationship = "dependent"
67-
description = "Bot orchestration platform (rhodibot, echidnabot, sustainabot, etc.)"
68-
interaction = "Ochrance triggers bot actions via repository_dispatch; bots enforce verification policies"
69-
url = "https://github.com/hyperpolymath/gitbot-fleet"
70-
71-
[[related-projects.project]]
72-
name = "rhodium-standard-repositories"
73-
relationship = "sibling-standard"
74-
description = "RSR compliance standard for repository structure"
75-
interaction = "Ochrance follows RSR for repository layout, CI workflows, and metadata"
76-
url = "https://github.com/hyperpolymath/rhodium-standard-repositories"
77-
78-
[integration-points]
79-
# External systems this project connects to
80-
81-
[[integration-points.system]]
82-
name = "echidna"
83-
direction = "bidirectional"
84-
protocol = "proof-dispatch"
85-
description = "Dispatches Idris2 proof obligations; receives synthesised proofs and confidence scores"
86-
87-
[[integration-points.system]]
88-
name = "hypatia"
89-
direction = "outbound"
90-
protocol = "logtalk-facts"
91-
description = "Emits verification reports as Logtalk facts for neurosymbolic CI/CD analysis"
92-
93-
[[integration-points.system]]
94-
name = "gitbot-fleet"
95-
direction = "outbound"
96-
protocol = "repository_dispatch"
97-
description = "Triggers bot orchestration events on verification status changes"
98-
99-
[[integration-points.system]]
100-
name = "ostree"
101-
direction = "outbound"
102-
protocol = "ostree-deploy"
103-
description = "Deployment target: verified filesystem images deployed via OSTree to Fedora Kinoite"
104-
105-
[[integration-points.system]]
106-
name = "hacl-star"
107-
direction = "inbound"
108-
protocol = "c-ffi-linking"
109-
description = "Links against HACL* verified cryptographic implementations (future crypto module)"
110-
111-
[what-this-is]
112-
descriptions = [
113-
"A modular verification framework for OS subsystem integrity",
114-
"An Idris2-based system for expressing and checking subsystem correctness guarantees",
115-
"A bridge between dependent-type theory and practical system deployment",
116-
"A framework with progressive strictness levels (Lax/Checked/Attested)",
117-
"A thesis-scope proof-of-concept targeting filesystem verification on Fedora Kinoite",
15+
projects = [
16+
"ochrance — canonical core and proof source of truth; implements the VerifiedSubsystem interface, A2ML parser, verified Merkle tree, and ECHIDNA FFI; harvested this repo's mode-indexed interface (D1)",
17+
"echidna — Rust/Julia neurosymbolic prover platform; Ochránce adds Idris2 as 13th backend (ADR-005)",
18+
"idris2-echidna — Idris2 prover abstraction layer for ECHIDNA dispatch",
19+
"svalinn — estate sibling; edge verification gateway; migrating ReScript → Ephapax (D3 in ochrance)",
20+
"valence-shell — consumes Ochránce attestation receipts for accountable state transitions",
21+
"echo-types — semantics of the residue/loss exposed by state transitions",
22+
"boj-server — SSG/build host (casket engine); ANCHOR parent (see anchors/ANCHOR.a2ml)",
23+
"verisimdb — vulnerability/weakness tracking database; ingests Hypatia scan results",
24+
"hypatia — neurosymbolic CI/CD intelligence; consumes Logtalk facts from verification runs",
11825
]
11926

120-
[what-this-is-not]
121-
descriptions = [
122-
"Not a replacement for Echidna -- Ochrance defines proof obligations, Echidna synthesises proofs",
123-
"Not a general-purpose theorem prover -- it is a verification framework for subsystem integrity",
124-
"Not limited to filesystems -- the framework supports any subsystem via the VerifiedSubsystem interface",
125-
"Not production-ready -- currently in design phase at 5% completion",
126-
"Not a runtime verification tool -- proofs are checked at compile time (Checked/Attested levels)",
27+
[integrations]
28+
# This repo is primarily docs; integration points are defined by spec, discharged in ochrance.
29+
declared = [
30+
"echidna — proof-obligation dispatch (ADR-005; planned)",
31+
"hypatia — Logtalk scan output on commit",
32+
"boj-server — ANCHOR parent (SSG build)",
12733
]

0 commit comments

Comments
 (0)