Currently under development Part of the OpenAI WebMCP Challenge Public release date

inite

Active product build

Finite / public build record

Built in public. Proven before claimed.

This is the deeper engineering record behind the product page: what exists, how the safety boundaries work and what the team is testing next.

Back to the product

Engineering / Codex for judgment, code for control

Codex proposes the change. Finite protects the plan.

Codex handles language and research. Finite's code handles arithmetic, constraints, persistence and approval.

Operator

Codex

Reads intent, researches evidence and prepares options.

47 WebMCP toolsPage-scoped · content-addressed
Control plane

Finite kernel

Checks constraints, binds revisions and rejects stale or unapproved writes.

Atomic repositoryOptimistic concurrency · exact retry
Accepted truth

D1

Commits the plan head, revision, receipt, events and evidence in one transaction.

01

One accepted truth

The current plan is an immutable revision with a replayable history.

02

Rules stay code

Conservation rules, locks and relationships run in code.

03

Research stays evidence

Prices, availability and other observations are stored with provenance and treated as untrusted.

04

Authority stays human

WebMCP cannot create an approval. Approval binds one candidate to one revision.

05

Writes fail closed

A failed write restores state and idempotency so the same operation can be retried.

06

Every change leaves proof

Each operation records input, result and plan-context hashes.

Current scopeFinite can model, compare and revise a plan. It does not yet change bookings, make purchases, pay suppliers or report that another system acted.

Build log / verified engineering

What has been built and tested.

Finite is under active engineering. This record changes after behavior passes its contract tests.

Finite's current public product surface showing the product promise and Paris whole-plan example.
Current public surface showing the Paris replanning example. Interface preview In active development. Layout and interaction may change before public release.

Current slice

The product now has a public front door.

The public page, authenticated kitchen and Codex operator use the same versioned plan. Access stays private while tenancy, recovery and the full consumer loop are tested.

  1. Build 08

    A fresh Codex task receives one next action.

    The entry packet checks arrival work against accepted-plan work and returns up to three routes grounded in current state. Suggestions, research, validated options and human decisions are stored as different states.

    Proven
  2. Build 07

    Codex can start from a short handoff.

    The handoff points a fresh task to finite_enter_kitchen. Finite returns the current arrival, accepted plan, authority state and next route. Plan contents stay in the product.

    Proven
  3. Build 06

    Site and Codex work can resume after a delay.

    Human input is append-only. Checkpoints, version checks and staged clarification prevent an older session from overwriting later plan state.

    Proven
  4. Build 05

    Travel, renovation and event compile to different surfaces.

    Travel uses a calendar, renovation uses a phase lane and event uses a run of show. Each surface has its own measures, language, entities and actions. State and approval rules remain shared.

    Proven
  5. Build 04

    Plan state commits atomically for each tenant.

    D1 commits the plan head, revision, receipt, domain event and evidence in one transaction. ChatGPT identity derives the tenant. Finite does not store the credential.

    Proven
  6. Build 03

    WebMCP cannot create human approval.

    Codex can orient, research, compare and stage. Approval creators sit outside WebMCP. Every consequential command binds to one candidate and revision.

    Locked

Current roadmap / ordered by product risk

Harden the full loop, then widen access.

Current work focuses on the consumer loop and recovery. Portability comes next. External actions will be added only when each connector has its own approval and receipt path.

Now / hardening

Test the full consumer loop.

  • Complete fresh-user Site-to-Codex journeys
  • Run recovery and export drills against plan history
  • Fuzz replanning properties and invariants
  • Set latency, rate and redacted telemetry budgets
Next / portability

Let another person own their kitchen.

  • Portable OIDC and self-hosted identity
  • Supported migration and first-run ownership
  • Recurring-period and milestone plan experiments
  • Independent-use acceptance before public beta
Later / external action

Add one connector at a time.

  • Booking, supplier and calendar connectors
  • Approval for each external action
  • Receipts for accepted and refused actions
  • Connector-specific permissions

Finite / product

The engineering exists to protect the experience.

Return to the product page to see the same planning engine adapt across travel, renovation, events and your own outcome.

Back to Finite