Foundation Plan Guide

Foundation Plan · sketch/0.23

From product meaning to an ordinary codebase.

A user and their existing agent author one reviewable Foundation Plan. First Draft imports that meaning, analyzes it against a pinned target, and compiles a Foundation the user can continue in ordinary source.

See how the system works Take the tour Open the Explorer

This is pre-alpha architecture, not a complete product demo. Bounded import, analysis, Compilation, Rails and selected-native emission, and publication slices exist; the complete authoring journey and full Foundation Plan coverage do not.

Current fixture set

3Plan sketches
—Structured definitions
—Explicit Rails choices
—Entities

The system in five moves

Meaning stays traceable all the way to source.

Each stage owns a different job. Keeping the Plan, Project graph, GapSet, and generated Foundation distinct is what lets the system stay reviewable without trapping the resulting application inside a proprietary runtime.

  1. 01

    Author the application

    The user and their existing agent turn product decisions into one complete Foundation Plan.

  2. 02

    Import one working graph

    The Project owns the mutable relational graph; its Head retains the exact submitted Plan bytes.

  3. 03

    Analyze before generating

    Whole-graph analysis checks meaning against the pinned target and records one exact GapSet of every skipped, partial, and unsupported consequence.

  4. 04

    Compile one reviewed snapshot

    Deterministic renderers consume the accepted graph and GapSet, then emit and verify a Foundation with the exact Plan and gaps beside it.

  5. 05

    Continue in ordinary source

    The user and agent own a normal codebase and keep building without a First Draft runtime.

Plan
The portable authored contract.
Project graph
The service's mutable working model.
GapSet
The exact reviewed support disclosure.
Foundation
The generated, verified, editable source.

What is in the document?

Five ideas, carried in one document.

The routed Project owns graph and revision identity. This self-contained document carries the exact application meaning, target pin, subject continuity, and readable links for import, export, review, and Compilation provenance.

Foundation Plan = subject continuity + application meaning + underivable facts + target profile + sparse material choices

01

Subject continuity and readable links

Each independently mutable subject carries a stable UUID and an owner-local key. Typed links remain readable scoped paths, while the Project route and server records own graph and revision identity.

02

Application definition

Product meaning expressed as Entities, Fields, relationships, rules, Policies, and Scaffolds. A state machine is one behavioral Field type, while Field notes may explain meaning without adding behavior.

03

Facts nothing can derive

A domain, brand colors, which native clients to build, and which delivery channels to wire. No Entity, Field, or Scaffold implies these, and each either supplies material the Compiler cannot invent or obliges the owner to obtain an external credential.

04

Target and profile

The platform to generate and the pinned set of generator rules, defaults, supported translations, derived prerequisites, and verification expectations.

05

Realization choices

Sparse material target-specific decisions that cannot be derived. The current sketch uses this only for exclusive arc versus polymorphic storage of a closed multi-target Reference.

The chapter example

Oscar Party starts with an ordinary relational model.

Movies connect to people through credits. Users bookmark and rate movies. The Rails profile fixes the current authentication and Field lowerings, so Oscar Party needs no explicit realization choice.

Structured in the Plan

The application model

  • Movie, Person, Credit, User, Bookmark, and Rating Entities
  • Date and result Predicates, compound uniqueness rules, and named relationship paths
  • Best Picture and watch state-machine Fields, including the watched-at timestamp callback
  • Movie-scoped Credit positions, fixed-currency production budget, and rich-text reviews

Outside this Plan

Product-specific catalog work

  • Provider search and identity matching
  • Importing release details and posters without overwriting edits
  • Keeping the watchlist useful during provider outages

Three documents, increasing pressure

Learn with Oscar Party, then test the edges.

Open the explorer →

Loading the current fixtures…

When you inspect a Plan

Four checks keep the boundary honest.

Use the definition browser and data model to trace the exact JSON. These questions test the proposed format; they do not assume it is final.