Backend Core
The backend operating system for controlled biological production.
AcreFrame is being built around the objects, events, reviews, and evidence trails that determine whether a regulated biological operation can move product, reconstruct decisions, and understand operating pressure.
Decision-support only. Human review required. No compliance certification, legal/regulatory advice, cultivation guidance, or autonomous facility control. Demo data is fictional.
Core v0 Scaffold
AcreFrame Core v0 is implemented as a demo scaffold
Core v0 ships with 18 typed entities, deterministic fictional demo data, a read-only repository layer, and five public API demo routes. It is not a production backend — it is a scaffold for design partner validation. Inspect the scaffold →
18
Typed entities
5
Public API routes
0
Live integrations
1
Demo facility
Modules
Twelve backend modules
Facility Registry
ImplementedDurable facility identity with rooms, zones, licenses, and responsible parties.
In: Facility metadata, room list, zone mappings, license references.
Out: Facility graph with room and zone identity.
Facility data is provided by the operator. AcreFrame does not verify regulatory status.
Room / Zone Model
ImplementedSpatial context for batches, signals, and environmental events.
In: Room labels, zone types, environmental setpoint references.
Out: Room and zone entities linked to batches and signals.
Room linkage is operator-confirmed. AcreFrame does not autonomously assign rooms.
Batch / Lot Graph
ImplementedAnchor object for movement, QA, packet, signal, and distribution context.
In: Batch logs, lot records, movement records, stage transitions.
Out: Batch entity with linked lots, QA state, packet readiness, movement status, decision history.
Batch links are suggestions. Humans confirm relationships and approve movement.
Evidence Store
ImplementedNormalized evidence with source attribution, ingestion timestamp, and completeness flags.
In: Exports, screenshots, spreadsheets, logs, document samples.
Out: Normalized evidence records with parsed metadata and gap flags.
Evidence is operator-provided. AcreFrame does not access systems without explicit export.
QA Hold Engine
ImplementedTrack hold state, aging, owner ambiguity, and linkage to batches and packet sections.
In: QA hold records, aging history, owner notes, retest logs.
Out: Hold entity with aging score, owner clarity, batch linkage, and packet gap attribution.
AcreFrame tracks holds. It does not release them or certify QA outcomes.
Packet Readiness Engine
ImplementedMap packet section completeness to movement gates and export readiness.
In: Packet sections, COA files, attestation records, export requirements.
Out: Packet gap matrix, readiness score, blocked-gate attribution.
Packet readiness is decision-support only. It does not certify compliance.
Signal Event Ledger
ImplementedStore normalized facility signals with room/batch linkage and anomaly flags.
In: Environmental sensor streams, equipment event logs, energy intervals.
Out: Normalized signal events with anomaly bands and review context.
Signal events enrich context. They do not trigger autonomous action.
Review Queue
ImplementedScore and route review items to qualified operators.
In: Failure chains, entity gaps, aging signals, owner ambiguity.
Out: Prioritized queue with owner assignment, evidence links, review windows.
Queue is decision-support. Humans decide what to review and when.
Decision Ledger
ImplementedPreserve human decisions with evidence attachments and unresolved item tracking.
In: Review outcomes, human decisions, evidence references.
Out: Immutable decision log with reconstructable audit trail.
Humans record decisions. AcreFrame preserves memory.
Cost Pressure Model
ImplementedLink inventory aging, distribution compression, and hold costs to batch-level exposure.
In: Inventory snapshots, distribution commitments, hold aging, rework records.
Out: Cost pressure events tied to batches and facility cycles.
Cost pressure is estimated from operator data. It does not guarantee financial outcomes.
Diligence Output Builder
ImplementedAssemble readiness reviews, exception taxonomies, and operating-loop maps.
In: Decision ledger, packet matrices, failure chains, entity snapshots.
Out: Facility Loop Review, Sample Report, risk taxonomy, dependency graph.
Diligence outputs are human-reviewed artifacts.
Read-Only Integration Layer
RoadmapIngest lawful exports from external systems without replacing them.
In: Seed-to-sale exports, task tool exports, inventory exports, environmental logs.
Out: Normalized records linked to the AcreFrame entity graph.
Does not replace regulated systems. Requires explicit operator export.
Events
Proposed event model
These event types describe the proposed design-partner architecture for the AcreFrame backend. They are not a live event stream today.
| Event | Description | Status |
|---|---|---|
| record.ingested | Evidence file received and attributed to source. | Design Partner |
| evidence.normalized | Raw evidence parsed into standardized schema. | Design Partner |
| entity.linked | Relationship detected between two entities. | Design Partner |
| batch.created | New batch entity instantiated from evidence. | Design Partner |
| batch.linked | Batch linked to room, lot, or owner. | Design Partner |
| qa_hold.created | QA hold detected from operator records. | Design Partner |
| qa_hold.aged | Hold age exceeded target window. | Design Partner |
| packet.section_missing | Required packet section incomplete or unattested. | Design Partner |
| signal.event_detected | Facility signal exceeded anomaly band. | Implemented |
| review.assigned | Review item routed to qualified operator. | Design Partner |
| decision.recorded | Human decision preserved with evidence references. | Design Partner |
| movement.blocked | Batch movement gate blocked by hold or packet gap. | Design Partner |
| distribution.dependency_detected | Distribution commitment conflicts with batch state. | Implemented |
| cost.pressure_updated | Inventory aging or compression updated cost exposure. | Implemented |
| packet.ready_for_review | Packet completeness threshold reached for human review. | Design Partner |
Data Boundary
What AcreFrame stores and what it does not own
AcreFrame stores
- Operational evidence from operator exports
- Normalized records with source attribution
- Entity relationships with confidence scores
- Failure chain paths and review queue state
- Packet gap matrices and readiness scores
- Human decisions with evidence references
- Signal events with room/batch linkage
AcreFrame does not own
- Regulatory truth or compliance certification
- Equipment control authority or autonomous commands
- The authority to release QA holds
- The authority to approve batch movement
- The authority to authorize distribution
- Cultivation, pesticide, nutrient, or watering prescriptions
- Formulation, extraction, or dosing instructions
Roadmap
Backend build sequence
Public architecture and Core v0 backend scaffold
ImplementedPublic website, Terminal demo with fictional data, Facility Loop Review service, architecture documentation, Core v0 typed entity model, five read-only API demo routes.
No live customer deployments. No real integrations. No production database.
Terminal and API routes serve fictional demo data only. No customer data.
Facility Loop Reviews
ImplementedPaid operating diagnostics, failure chain mapping, exception taxonomy, readiness scorecard.
Not software-as-a-service. Not autonomous. Not a compliance certification.
Human-reviewed artifacts only.
Design Partner Backend Object Model
Design PartnerFacility Registry, Room/Zone Model, Batch/Lot Graph, Evidence Store, QA Hold Engine.
Not a seed-to-sale replacement. Not a universal integration layer.
Object model is tuned per design partner.
Evidence Graph + Review Queue
Design PartnerEntity linking, failure chain detection, review scoring, owner routing.
Does not predict the future. Does not replace human judgment.
Queue is decision-support only.
Packet Readiness Engine
Design PartnerPacket gap matrix, COA chain tracking, movement-gate attribution.
Does not certify compliance. Does not guarantee inspection outcomes.
Packet readiness is a decision-support artifact.
Read-Only Integrations
RoadmapLawful export ingestion from seed-to-sale, task tools, inventory systems, environmental logs.
Does not replace regulated systems. Does not access live databases without consent.
Requires explicit operator export.
Signal Bridge
RoadmapRead-only environmental signal ingestion, anomaly banding, room/batch linkage.
Does not control equipment. Does not trigger autonomous action.
Read-only by design.
Multi-Facility Operating Memory
Not OfferedCross-facility entity graphs, shared taxonomy, consolidated decision logs, institutional reporting.
Not currently offered. Future infrastructure stage only.
Corporate operations lead reviews multi-facility memory.
Design partner
Shape the backend object model.
If you are a licensed operator with real records and structured workflows, request a Facility Loop Review to scope design-partner fit.
AcreFrame does not provide legal advice or regulatory advice. AcreFrame does not provide pesticide guidance, cultivation treatment instructions, irrigation or watering prescriptions, or nutrient dosing prescriptions. No pesticide. No cultivation treatment prescriptions. AcreFrame does not autonomously control HVAC, irrigation, lighting, water systems, dosing, QA release, remediation, harvest, packaging, shipment, or compliance decisions. No autonomous control. Qualified human review required. AcreFrame does not provide compliance certification. No compliance certification. AcreFrame does not guarantee compliance, yield, potency, margin, savings, audit outcomes, or risk elimination. Licensed operators only where lawful.