ROOKWELD / PROCESS ARCHIVE

The work behind
the work.

BUILT SYSTEMS · EXPERIMENTS · DECISIONS · EVOLVING CANON
NOTE / 01MIND FOUNDRY → REALITYOSEVOLVING SYSTEM
NOTE / 02FORGECARE ENGINEERINGVERIFIED SLICE
NOTE / 03BUILDING THE MIDNIGHT LINETRANSMEDIA PROCESS
OPEN THE NOTEBOOK ↓

00 / WHY THESE NOTES EXIST

Finished work shows
the result. Process shows judgment.

Forge Notes documents what was built, what was learned and what remains unresolved. The point is not to make every experiment sound finished. It is to make the path inspectable.

Prototype, product and possibility
deserve different labels.

FORGE NOTE / 01 · SYSTEM EVOLUTION

From MindFoundry
to RealityOS.

STATUSRUNTIME VERIFIED

Six services, the full smoke suite and key local-agent workflows passed against disposable test data.

RealityOS did not begin as a grand platform diagram. It began as a working launcher and accumulated harder questions: which model should answer, what should be remembered, how should tools be governed and where should each workload run?

01
BUILT

MindFoundry Micro

A functional Python and PySide6 desktop launcher using Ollama, with model switching, session persistence, hybrid local/GPT fallback and Obsidian logging.

02
PROTOTYPED

Adaptive orchestration

Experiments in routing, telemetry, diagnostics, encrypted persistence and feedback-driven model selection.

03
RUNTIME VERIFIED

RealityOS

A substantial local-first prototype whose six services, routed chat, pipelines, streaming and disposable workflows passed controlled verification.

04
NEXT HARDENING

Repeatability and security

Add frontend automation, verify the installed desktop UX and harden tool, watcher and memory boundaries.

INTERFACETauri launcher
→
ORCHESTRATIONRouting / pipelines
→
CONTEXTMemory / timeline
→
EXECUTIONTools / local services
THE HONEST VERSION

A controlled disposable-data pass verified all six services, the 16-check smoke suite, local-model chat, classifier routing, a named pipeline, streaming, scheduler execution, node routing and installer builds. RealityOS is runtime-verified as an evolving prototype—not claimed as production-ready.

OPEN THE RUNTIME-VERIFIED CASE STUDY →

FORGE NOTE / 02 · ENGINEERING SLICE

Evidence that survives
the interface.

SLICE STATUSVERIFIED

Research-branch engineering work. Separate from the public v1.0.0 product-release version.

Startup Intelligence explored how ForgeCare could inspect startup entries conservatively without turning uncertainty into false confidence.

The intelligence layer was deliberately isolated from the existing scanner and live UI. It produces immutable analysis that can be projected into privacy-safe Evidence and reloaded without changing meaning.

EXISTING PATHStartupScanner→StartupItem[]→SystemSnapshot→StartupImpactService→StartupManagerService
INTELLIGENCE SLICEDeterministic analysis→Privacy-safe projection→EvidenceService→Schema-1 reload→Evidence Explorer
186TESTS PASSED

0 failed · 0 skipped

0BUILD WARNINGS

Restore, build and test verified

1PRODUCTION ENUM CHANGE

Existing generic Explorer required no production change

01

Unknown stays unknown

Classification remains deterministic and conservative when evidence is incomplete.

02

Privacy before persistence

Paths and correlation keys are normalized before evidence crosses the repository boundary.

03

Integration after proof

No live collection or MainWindow integration was claimed as complete. The vertical slice was verified first.

Read the product case →
The Midnight Express to Nowhere crossing a frozen landscape
THE MIDNIGHT LINEFROM RULE → SCENE → SHOT → SOUND

FORGE NOTE / 03 · TRANSMEDIA DEVELOPMENT

One world.
Several forms.

The Midnight Line was designed so no single medium owns the truth. The world bible protects the rules; the screenplay tests them through action; the storyboard turns action into rhythm; music gives characters a voice.

01

Creative premise

A moving refuge, impossible fares and a train that answers need rather than maps.

02

World Bible v0.1

A 35-page creative operating system separating locked canon, provisional direction and deliberately withheld mysteries.

03

The First Ticket

A provisional 5–8 minute cinematic prologue screenplay dated 19 August 2026.

04

Cinematic storyboard

A 32-shot, 07:05 visual plan across eight escalating spaces, including visual grammar and sound arc.

05

Music & visual language

Character songs, soot-black rail imagery, aged brass, cyan forge-light and a black-feather emblem.

LOCKED

Approved canon future work must preserve.

PROVISIONAL

Strong direction kept intentionally revisable.

WITHHELD

A mystery protected from definitive explanation.

“Strange enough to inspire wonder;
human enough to hurt.”

04 / THE RECURRING METHOD

Different mediums.
The same discipline.

Whether the output is software, infrastructure or myth, the useful pattern remains surprisingly consistent.

01

Define what is true

Start with evidence, canon or a working constraint—not the desired marketing sentence.

02

Build one useful path

Prove a vertical slice before expanding the surrounding system.

03

Preserve uncertainty

Unknown is an honest state in both engineering and storytelling.

04

Leave a trail

Tests, documents, diagrams and artifacts make decisions reviewable later.

THE NOTEBOOK REMAINS OPEN

Build it.
Question it. Document it.

Enter the Workshop →Return to Studio ↗