What this is: the self-contained working surface for implementing OFARM2 — a Kernel/Core/Platform implementation and conformance packaging profile plus the Slovenia plant-protection record-keeping pilot definition. Designed to be lifted into its own repository unchanged.
For agents and new contributors: start with AGENTS.md (binding working rules), DECISIONS.md (settled decisions), and M1_BRIEF.md (historical M1 kernel-build brief and scope anchor). M0 — verification and grounding — is CLOSED as of 2026-06-12; see profile_si_ffs/M0_DESK_RESEARCH.md for the ledger.
What this is not: OFARM law. This package is a derived implementation/conformance artifact under PROJECT_AUTHORITY.md (carried verbatim in reference/law/). It creates no new authority, overrides nothing, and promotes nothing. New schemas here are candidate artifacts (Constitution RC2.1 §6.16) pending post-pilot governance.
No production readiness of any kind is claimed: not software-delivery, model-deployment, certification, legal/security/compliance advice, external-standard readiness, live-registry integration, autonomous anything, or current/default schema promotion. The pilot claims record-keeping completeness only — explicitly not current-compliance against the authorisation register (see PILOT_SI.md).
profile_nl_go_glmc7_2026/ is a narrow legal-source/conformance-ready profile slice for 2026 Netherlands GO + GLMC 7 under its own release posture. That posture is limited to the profile/source standard and does not change the repository's runtime, platform, external-standard, or whole-country claim limits.
KERNEL.md— the truth machine: 12 record families, 7 rules, the reachability invariant, conformance definitionCORE.md— crop-farming semantics on the Kernel; the operation chain; code-binding disciplinePLATFORM.md— the pilot runtime: components, gate pipeline, storage posture, invalidation, unsupported surfacesPILOT_SI.md— Slovenia pilot: claim scope, review policy, milestones M0–M4, success/kill criteriaCAPTURE_MAPPING.md— the five things a farmer touches; everything else auto-populatedprofile_si_ffs/PROFILE.md— scheme roles, currentness posture, evidence/review policy, shipped + deferred instancesprofile_nl_go_glmc7_2026/README.md- narrow Netherlands GO + GLMC 7 2026 profile sliceprofile_si_ffs/views/VIEWS.md— the two SI pilot governed outputs, specifiedconformance/CONFORMANCE.md— package self-check + platform MVP plus root conformance regression suite
KERNEL.md CORE.md PLATFORM.md PILOT_SI.md CAPTURE_MAPPING.md ERRATA.md
contracts/ kernel/ (23 extracted + 3 candidate) core/ (11 extracted + 5 candidate)
platform/ (10 extracted) CONTRACTS_MANIFEST.json (digests + provenance)
profile_si_ffs/ PROFILE.md + 6 descriptor-bootstrapped validated instances (activation set,
artifact set, context snapshot, code-binding profile, 2 reference snapshots)
+ generated/verified Capability Manifest + UNSUPPORTED_SURFACES.md
+ views/ (SI view specs/artifacts) + extraction_inventory/ (documentation-only inventory)
profile_nl_go_glmc7_2026/ narrow Netherlands GO + GLMC 7 2026 profile/source slice
views/ VIEWS.md pointer to profile-local SI view material
kernel/ the M1 implementation: store, gates, materializer, views, manifest, API, conformance tests
conformance/ ofarm_pkg_contract_check.py + CONFORMANCE.md + fixtures/gate_sequencing/ (9 inherited)
+ evidence/ (executed platform-MVP suite results)
reference/ REFERENCE_MANIFEST.json + law/ (4) + rfcs/ (14) + research/ (1) + companions/
Honest count: ~52 contracts and instances, ~20 reference files, ~95 files total — small next to the canonical repository's ~4,800, not "tiny."
- Currentness note (package cut date):
2026-06-12is the Slovenia-local package cut date. The source packet was generated2026-06-11T22:41:01ZUTC (= 00:41 CEST, 2026-06-12) — seeprofile_si_ffs/source_packet_extracts/source_manifest.json. M0-closure and handoff dates throughout the package use the Slovenia-local date; the UTC timestamp is preserved in the source manifest. The package is not future-dated. - Law freeze (this repository): findings go to
ERRATA.mdonly — never into reference copies or as new law. The canonical repository evolves in parallel under steward governance; its changes are absorbed here by extraction with provenance (seeDECISIONS.mdD15). - Reference lane: verbatim, read-only, non-normative within the package, budget ≤ 30 files; additions require a manifest entry with a reason.
- Verification:
python3 conformance/ofarm_pkg_contract_check.pymust pass before any commit touching the package. - Provenance: every extracted file's source path, repo commit, and sha256 live in the manifests. Within the parent repository the reference copies are redundant by design — the package is built to travel.