Built by an operator who needed the record
ERRA began with a practical question: why should the formula, label, supplier evidence, batch record, and recall path disagree when they describe the same product?
Why ERRA exists
Johnny Curl founded ERRA around a recurring operating problem: formulas lived in spreadsheets, supplier evidence lived in email, labels lived in design files, and the history behind an approval lived in someone's memory. Each file could look correct while the full record contradicted itself.
ERRA was built to hold those relationships in one governed system. Ingredient and supplier facts feed the formula. The approved formula feeds the panel and the production record. Received lots feed the batch. The finished lot feeds the shipment and recall scope. Named people make the decisions, and the audit trail keeps them.
How the product is built
- Regulatory math is deterministic code with test fixtures, not generated text.
- Released formula versions are immutable. A change creates a new version and keeps the earlier record.
- Missing evidence remains missing. The system does not guess a passing result.
- Approvals identify the person, decision, record state, and time.
- Each organization owns its controlled records and chooses what to share with a counterparty.
- Customers can export their records instead of depending on a locked account.
Public identity
ERRA publishes its company identity consistently so customers, search engines, and research tools can tell this company from unrelated uses of the name. The public profiles below point back to this site.
What a governed record means here
ERRA reads the record the work leaves behind. Paying for software does not change what that record shows.
Recorded and shared through ERRA.
ERRA performs deterministic regulatory math and records operational decisions. It does not provide legal advice or replace the responsible company's quality and regulatory judgment.