Experience layer
Premium Next.js surfaces for public narrative, operator cockpit, control rooms and verification views.
Architecture
The FridayOS stack is built as layered control, not scattered automation.
Every layer has a job: present the system, check policy, select routes, persist runtime evidence and verify release readiness.
stack modelExperience → Policy → Routing → Memory → Verification
FridayOS should make every important path visible, gated, observable and testable.
Architecture layers
Control policy layer
Identity, workspace, firewall, write-policy and approval checks decide what agents are allowed to do.
Routing layer
Agent specs, provider policy, fallback selection, provider health probes and budget rules choose execution paths.
Runtime memory layer
Jobs, ledgers, activities, artifacts, reviews, usage and black-box audits persist what happened.
Verification layer
Readiness, diagnostics, production gates, live signals and test coverage protect release decisions.
Execution data flow
Work request enters a workspace
The task is interpreted with a target workspace, actor identity, candidate agent and intended tool/provider surface.
Policy checks narrow what is allowed
Identity boundary, workspace validation, firewall risk and write-policy checks decide whether the request is allowed, blocked or requires review.
Provider and agent route is selected
Provider router and health probes choose the safest available provider/model path with fallback and budget awareness.
Runtime stores preserve the evidence
Jobs, activity, usage, artifacts, reviews and ledger records keep the action replayable after execution.
Release gates summarize readiness
Diagnostics, readiness and production gates expose blockers before the system is treated as shippable.