System Architecture

EdgeRecord's current architecture is service-led with private-pilot automation. This page describes the intended evidence flow without overstating public self-serve availability.

Evidence flow

1. Capture baseline: collect the system state, approval context, and expected rollback path before a change begins.
2. Record action: document the actor, timestamp, scope, and meaningful change event.
3. Attach evidence: preserve hashes, logs, screenshots, exports, checks, or approval references.
4. Seal receipt: produce a canonical record hash and, when applicable, link it to the previous record hash.
5. Verify and hand off: deliver the receipt, human summary, and evidence package in a form the customer can archive.

Current surfaces

• Public website: Joomla-hosted product, trust, pricing, and documentation pages.
• Service workflow: scoped evidence packages prepared for customers and partners.
• Private-pilot API/CLI: controlled access for teams that need programmatic receipt submission and verification.
• Evidence package: plain-text or JSON receipt plus supporting artifacts.

Design constraints

• Receipts should be readable without production-system access.
• Verification should not depend only on trusting the hosted service.
• Human summaries must not claim more than the attached evidence proves.