Engineering Log
What is being built and why.
This log records architecture decisions, build notes, boundary clarifications, and known limitations. It does not fake production history, customer deployments, or live integrations.
Decision-support only. Human review required. No compliance certification, legal/regulatory advice, cultivation guidance, or autonomous facility control. Demo data is fictional.
Entries
Build notes and architecture decisions
Failure Chain architecture added to public product language
Architecture NoteImplementedPublic product language now models facility risk as connected failure chains across batch, QA, packet, signal, owner, distribution, and cost surfaces. Terminal demo surfaces render these chains as interactive dependency graphs.
Failure chains are decision-support only. They do not predict the future or certify risk.
Visual QA and smoke route baseline established
QA NoteImplementedPlaywright visual QA now validates 7 core pages across 6 viewports (390, 430, 768, 1024, 1440, 1920). Smoke route tests validate 25 routes return HTTP 200. Guard tests enforce forbidden claims, brand boundaries, metadata quality, href hygiene, and scoring correctness.
QA validates static pages and fictional demo surfaces. No production customer data is tested.
Backend object model defined for design partner scope
Architecture NoteRoadmapAcreFrame Core requires durable entities for Facility, Room, Zone, Batch, Lot, Material, Inventory Item, QA Hold, Packet Section, COA Record, Evidence File, Signal Event, Task, Review Owner, Decision Memo, Distribution Commitment, and Cost Pressure Event.
Object model is proposed schema direction. Real database schema will be co-designed with design partners.
Signal Bridge scoped as read-only roadmap capability
Boundary NoteRoadmapSignal Bridge is positioned only as a future read-only signal ingestion layer. It normalizes environmental records, equipment events, and room-level context linked to batches and QA holds for qualified human review.
Signal Bridge does not control HVAC, irrigation, lighting, dosing, QA release, movement, or shipment approval.
Decision Ledger scoped for human-reviewed operating memory
Build NoteRoadmapDecision Ledger will preserve who reviewed what, what evidence was attached, what remained unresolved, and what decision was recorded. Each memo links to batch, evidence files, and review owner.
AcreFrame preserves what humans decided. It does not make decisions.
Packet Readiness Engine architecture defined
Architecture NoteRoadmapPacket Readiness Engine maps packet section completeness to batch movement gates, COA chains, and export readiness. It produces a gap matrix with owner attribution and blocked-gate identification.
Packet readiness is a decision-support artifact. It does not certify compliance or guarantee inspection outcomes.
Evidence Normalization layer designed for heterogeneous inputs
Architecture NoteRoadmapEvidence Normalization parses exports, screenshots, spreadsheets, and logs into a consistent schema with standardized timestamps, units, and completeness flags. Normalization rules will be tuned per design partner.
Normalization does not judge record validity. It only standardizes format and flags gaps.
Review Queue scoring model defined
Design DecisionRoadmapReview Queue scores items by severity, age, dependency depth, and owner clarity. The scoring model is deterministic and tunable per facility. It routes items to qualified operators with evidence links and review windows.
Queue prioritization is decision-support only. Humans decide what to review and when.
Read-Only Integration Layer scoped for lawful exports
Boundary NoteRoadmapRead-Only Integration Layer will ingest lawful exports from seed-to-sale systems, task tools, inventory systems, and environmental logs. It will not replace regulated systems or access live databases without explicit operator consent.
Requires explicit operator export. Does not replace regulated systems.
Multi-Facility Operating Memory deferred to future stage
Architecture NoteRoadmapCross-facility entity graphs, shared taxonomy, consolidated decision logs, and institutional reporting surfaces are scoped as future infrastructure. Not offered in current design partner engagements.
Not currently offered. Future infrastructure stage only.
Core v0 backend scaffold implemented with typed entity model
Build NoteImplementedAcreFrame Core v0 ships with 18 typed entities, deterministic fictional demo data for Northline facility, a read-only repository layer, and five force-static API demo routes. The Terminal now consumes Core data through a compatibility adapter. All objects include fictionalDemo flags and boundary annotations.
Core v0 is demo scaffold only. Not a production backend. No persistent database. No customer data.
Core v0 public API routes published
Build NoteImplementedFive read-only API routes are now public under /api/core/demo/: facility graph, terminal snapshot, review queue, packet readiness, and event ledger. All routes include boundary metadata and disclaimers. They are force-static and prerender at build time.
API routes return fictional demo data only. No authentication required because data is public fiction. Not suitable for production use.
Core-Demo public page created for backend visibility
Build NoteImplementedThe /core-demo page surfaces the full Core v0 facility graph, API endpoint catalog, and boundary metadata for visitors who want to inspect the backend scaffold without opening the Terminal.
Core-Demo surfaces the same fictional data as the Terminal and API routes. Not customer data.
Limitations
Known limitations
- No live production database. Core v0 uses deterministic in-memory demo data.
- No real sensor integrations. Signal Bridge signals are fictional demo data.
- No live customer deployments. Design partner engagements are qualification-stage.
- No seed-to-sale system replacement. Integrations are read-only export ingestion only.
- No automated QA release, batch approval, or shipment authorization.
- No compliance certification or regulatory approval claims.
- No live API consumers. Core demo routes are public but unauthenticated read-only.
Next
Next engineering dependencies
- Design partner facility with real records for object model validation.
- Export format samples from seed-to-sale, task, inventory, and environmental systems.
- QA hold and packet section schema agreement with design partner compliance lead.
- Signal Bridge hardware partner for read-only sensor ingestion prototype.
- Decision Ledger UX validation with operator supervisors.
- Core v0 to v1 migration: replace in-memory data with persistent database layer.
- Authentication and authorization layer for design partner API access.
Repository signal
Current build state
Branch: main
Working tree: clean
Build: 39 static pages prerendered
Tests: 8 guard suites pass
Visual QA: 78 tests across 6 viewports pass
Smoke routes: 32 routes return HTTP 200
Core v0: 18 typed entities, 5 API demo routes, deterministic in-memory data
Design partner
Contribute to the build log.
If you are a licensed operator with real operating complexity, request a Facility Loop Review to shape the next engineering dependencies.
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.