OFARM 2 current development baseline

What is OFARM?

OFARM is an open semantic reference model and governance framework for crop-farming operations. It defines how farm operational facts, evidence, authority, events, current state, queries, outputs, packs, and machine-readable contracts should be represented so that systems can remain traceable, interoperable, and auditable.

OFARM is assertion/history-first: the authoritative record is the governed history of assertions, events, evidence, and review decisions; current state is a controlled materialization derived from that history, not a hidden truth store. OFARM also separates compliance-grade truth from advisory reasoning while keeping both grounded in one shared semantic substrate.

OFARM is meant to help developers, researchers, standards workers, and AI-assisted platform builders create farming systems that can explain what they know, where it came from, who had authority, and what can safely be done with it. It is not itself a production farm-management product, robotics runtime, certification service, legal-advice system, or autonomous farming system. For canonical authority and current read order, continue with PROJECT_AUTHORITY.md and CURRENT_ACTIVE_ENTRYPOINT.md.

Current package: OFARM2_2026-05-30_cp15_agentic_software_delivery_model_deployment_governance_merged_v0_2_final_currentness_normalized.

Latest controlled amendment: CP15 — Agentic Software Delivery and Model Deployment Governance.

CP11, CP12, CP13, and CP14 remain active where merged. CP15 is the current controlled-amendment endpoint. CP15 does not promote CP11, CP12, CP13, CP14, or CP15 machine contracts to current/default.

This repository now reads as a clean materialized CP15 development baseline:

1. Current material first.
2. Lineage second.
3. Archive/history third.

The current/ folders and 03_machine_contracts/currentness/ are reader views and control views. They are not new law, do not override canonical authority, and do not replace the canonical active files.

Current read path

1. PROJECT_AUTHORITY.md
2. ACTIVE_SUBSTANCE_README.md
3. CURRENT_ACTIVE_ENTRYPOINT.md
4. CURRENT_ACTIVE_ENTRYPOINT.json
5. README.md
6. 00_active_baseline/current/CURRENT_BASELINE_VIEW.md
7. 00_active_baseline/current/CURRENT_BASELINE_VIEW.json
8. 00_active_baseline/OFARM_Reference_Model_and_Artifact_Constitution_RC2_1.md
9. 00_active_baseline/OFARM_Platform_Runtime_and_Product_Architecture_RC2_1.md
10. 00_active_baseline/OFARM_Alignment_Register_v0_13.md
11. 00_active_baseline/OFARM_post_gap_closure_readiness_gate_memo_v0_1.md
12. 00_active_baseline/OFARM_final_hostile_review_after_gap_closure_v0_1.md
13. 02_accepted_rfcs/current/CURRENT_ACCEPTED_RFC_VIEW.md
14. 01_companion_artifacts/current/CURRENT_COMPANION_ARTIFACTS_VIEW.md
15. 03_machine_contracts/currentness/CURRENT_MACHINE_CONTRACTS_VIEW.md
16. 04_implementation_and_conformance/README.md
17. package_meta/history/controlled_amendments/README.md
18. package_meta/history/currentness_overlays/README.md

Authority boundary

Active authority order is governed by PROJECT_AUTHORITY.md:

1. 00_active_baseline/
2. 02_accepted_rfcs/
3. 01_companion_artifacts/
4. 03_machine_contracts/

Supporting implementation, handoff, research, linked-domain context, package metadata, history, archive, and legacy folders do not override active authority.

Current views

• 00_active_baseline/current/CURRENT_BASELINE_VIEW.md
• 00_active_baseline/current/CURRENT_BASELINE_VIEW.json
• 01_companion_artifacts/current/CURRENT_COMPANION_ARTIFACTS_VIEW.md
• 01_companion_artifacts/current/CURRENT_COMPANION_ARTIFACTS_VIEW.json
• 02_accepted_rfcs/current/CURRENT_ACCEPTED_RFC_VIEW.md
• 02_accepted_rfcs/current/CURRENT_ACCEPTED_RFC_VIEW.json
• 03_machine_contracts/currentness/CURRENT_MACHINE_CONTRACTS_VIEW.md
• 03_machine_contracts/currentness/CURRENT_MACHINE_CONTRACTS_VIEW.json

Lineage and history

Clean-baseline migration ledgers, reconciliation records, release-profile split proof, and phase-report snapshots live in package_meta/history/clean_baseline_migration/. Only package_meta/history/clean_baseline_migration/ledgers/ is current canonical migration proof; phase-report contents are historical snapshots.

CP11 through CP15 package-meta controlled-amendment evidence lives in package_meta/history/controlled_amendments/. That lane is provenance and rollback evidence only; it is not default development reading and does not create new law.

Pre-Phase 5 layered currentness prose is preserved in package_meta/history/currentness_overlays/. Old package identities in that folder are historical/provenance references only.

legacy_reference/ remains contextual only, non-default, and never overrides active OFARM 2 law. 07_linked_domain_architectures/ remains root-visible as non-default active supporting context.

Not claimed

CP15 does not claim production software-delivery readiness, production model-deployment readiness, generated-adapter production readiness, cybersecurity certification, autonomous release readiness, full CI/CD product readiness, generic MLOps platform readiness, cloud/vendor deployment architecture readiness, legal/security/compliance advice, or automatic current/default schema promotion.

Validation posture

Full repository validation completed in Phase 8. Final verdict: ACCEPT_AS_CLEAN_BASELINE. Final package readiness: READY_FOR_FINAL_PACKAGE.

Bulky final ZIP and report ZIP artifacts are release assets outside the source-tree content. Final clean-baseline package metadata and validation logs live in package_meta/release/final_clean_baseline/.