Build log: September 25 to October 15
Three weeks of building Paragon, one step from each day. Most days had dozens of smaller changes; these are the ones that moved it forward. Where something failed, the failure is listed too, because it stays on record next to the passes.
Jump to Sep 25 – Oct 1 · Oct 2 – 8 · Oct 9 – 15
Sep 25 – Oct 1: foundations
The first kernel path runs the same way every time
Session 01 of the rebuilt Paragon went in: a deterministic path through the kernel, with its database schema and rules checked on a development copy of PostgreSQL.
On record. That day, the hosted database couldn't be reached because of a DNS problem. It was written down, not worked around.
Memory that scores what it learns
Adaptive memory and information scoring, which decide what's worth keeping and how far to trust it, ran against PostgreSQL. A recovery path can now rebuild knowledge from its source references, and the desktop shell with its eleven themes was connected to the local launcher.
A watchdog for the permission layer
Jack10, the layer that decides what's allowed, got a watchdog that checks its rules haven't changed while Paragon is running. Long tasks also got cutoff priorities and reflection gates: points where work stops to check itself before it continues.
On record. A live check of the Truth Protocol found a regression. It's recorded as a failure.
Every task moves through saved phases
The Turn Protocol arrived. Each task, or turn, now moves through measured phases that are saved as it goes, so its progress survives a crash. The day ended with the first Paragon V1 0.1.0 bootstrap pack: the baseline, the specification and the decision records in one verified bundle.
Hard stops, and a record that only grows
The scheduler now enforces hard time limits on background work. The run log became append-only: entries can be added, never edited or removed.
One trunk instead of many branches
Parallel lines of work were merged into one development branch, step by step, with a check at each step. The merge brought in a Wolfram route, so math claims are computed instead of guessed.
On record. A four-course live run failed at several points the same day. The failures and the comparison are kept.
Checkpoint 6
A frozen, tested version became the trusted base. It was sealed in a byte-exact archive, with what it doesn't cover written down beside what it does.
Oct 2 – 8: the prototype takes shape
Thinking locally
Bonsai, PrismML's compressed Qwen model, passed its first bounded reasoning test inside Paragon on a home graphics card. Two earlier attempts failed, and they stay on record next to the pass.
Dream State waits for you
Dream State now needs that day's approval from a person before it starts. If the approval can't be checked, it refuses instead of guessing. The task-tracking tests passed on both SQLite and PostgreSQL, including one where the process is stopped in the middle of a save.
The local model reads first
Every prompt now gets a brief from the local model before any cloud Director sees it. The desktop app became a proper window, with a read-only view of the Dream State Floor.
A space for each person
Each person sharing a Paragon machine now gets their own instance, with an owner-set lock and a review step before anything is delivered. Paragon also saves when it opens and takes a verified backup every day. The same day, this site came together, with the Dream State demo, the reference tests and the first post on this blog.
A smaller model at the front door
Phi-4-mini, Microsoft's small open model, now reads requests first. Bonsai loads only when a task needs it, and a heat guard watches the graphics card.
Hot hardware waits its turn
Local model work now passes a temperature check and a shared task budget before it starts. A cancel request now reaches every part of a running task.
Approval belongs to the work it approved
If the work behind a Dream State job changes after it was approved, the job is held instead of run. Daily setup stops when its rules can't be confirmed.
Oct 9 – 15: approvals and a kernel that stays up
Review cards with real choices
When Jack10 asks a person to review something, the card now shows the full task and its evidence. The choice you make there applies only to that task.
A fingerprint on the phone that asked
Approving from a phone now takes a fingerprint signature from the device that made the request, and every high-risk step requires one.
Thirty seconds to sign
The final fingerprint approval now expires after thirty seconds. On a real phone, an expired signature and an unregistered fingerprint were both refused.
On record. An experimental adapter for the smaller local model was finished as software but failed its live check. That result is kept.
A calmer desktop
The desktop app got a plain-language look: three status lamps, short page names, and the technical detail behind a Details switch. Every feature underneath stayed the same.
Every step saved as it happens
TurnSave records each task step by step while it runs, separately for each person, and reconciles an interrupted task after a crash. A resident kernel was proposed to keep Paragon running between sessions.
The kernel stays up
The resident kernel restarts a part of Paragon that crashes, recovers on a schedule, and starts again on its own at sign-in. Builds now run in contained workspaces that Paragon creates and cleans up itself.
Checkpoint 7, with its limits written down
The kernel, its supervision, sign-in startup, the new desktop look and contained builds were accepted as checkpoint 7. Of 4,588 test cases, 4,403 passed and 185 were skipped; none failed.
On record. Not covered by this checkpoint: Dream State, memory, fingerprint approval and security, and recovering when the supervisor itself crashes. That last one is next.
Want the next log in your inbox? Pick monthly progress and you'll get what moved forward each month.