How we build & verify
Architecture principles, evidence practice and the open-source software we build on.
- Status registry
- Checked
- Registry entries
- 25 entries
- 01Ethen product
- 02Platform gatewayOwned by the Platform
- 03Policy check (Sentinel)
- 04Approval by a person, when required
- 05Model or worker runs
- 06Record kept for review
01Authority
Platform authority model
Ethen products are designed not to rebuild model access, policy and approvals each on their own. They call the shared Platform, which owns those decisions.
- Where it stands
- That is the design. The Platform is in a gated preview and most of its subsystems are in development; the chips below come from the status registry.
Generated, not typed
Where the evidence stands
Generated from the status registry and the website's dependency data.
- 25Registry entriesProducts, technology areas and site resources.
- 20ImplementedEntries whose highest rung is Implemented.
- 0Locally testedEntries whose highest rung is Locally tested.
- 0Independently verifiedEntries whose highest rung is Independently verified.
- 86Open-source packagesListed on the third-party notices page.
The highest rung any registry entry has reached is Implemented. Rungs above it have no entries yet. Last checked 2026-10-31.
Read the transparency page02System
Subsystems
Each subsystem has one owner, the Platform. Status labels come from the status registry.
- 01Platform / GatewayPreview
Ethen Platform is the shared layer behind Ethen products: gateway, policy, approvals, flow, compute and computer use.
- 02Flow / AutomationIn development
Flow is the connector, vault, retrieval, automation and event subsystem of Platform.
- 03Sentinel / SecurityIn development
Sentinel is Platform's policy and defensive-security layer.
- 04GPU ComputeIn development
Compute is the Platform subsystem planned to schedule GPU workloads.
- 05Computer WorkerIn development
Computer is an isolated, lease-governed browser worker owned by Platform.
03Foundation
Foundation: contracts & tokens
Token values are not final, and the design system has not been released.
- 01Foundation / Design SystemIn development
Shared contracts, tokens and an accessibility test harness keep Ethen products consistent
04Practice
Test & evidence practice
- Gates
- This website's repository defines automated gates: type checks, unit tests, a production build, a smoke test, a style-coverage crawl, performance budgets, a redirect check and a claims check that rejects banned or unsupported wording.
- Verification
- A developer's passing run is not verification. Independent verification is a separate step, run by a different reviewer from a fresh copy of the code.
- 8Production-validated0
- 7Deployed0
- 6Protected-preview verified0
- 5Independently verified0
- 4Locally tested0
- 3Implemented20
- 2Source acquired4
- 1Proposed1
05Open source
Open-source software
Projects behind Ethen products are listed once a public page names them; the rest are under licence review.
86
open-source packages in this website, each listed with its licence and attribution.
- 0BSD
- Apache-2.0
- ISC
- MIT
06Questions