The Web of Alignment
FFFrame MVP Control Surface
Build the loop
Build the first alignment loop, then earn the right to expand it.
The active product line is simple on purpose: sign up, consent, baseline, interpreted output, history, and return check-in. The system grows later. The first loop has to feel real now.
Scope
FFFrame only
Current phase
First app loop
Build posture
From scaffold to signal
Loop sequence
- 01
Sign up and consent
Create the account, capture trust surfaces, and establish the user state cleanly.
- 02
Take the FFFrame baseline
Run the first real baseline module with a sealed scoring service behind the app.
- 03
Receive interpreted output
Show the user a Web Guide reading without exposing raw scoring internals.
- 04
Return for the next check-in
Make movement visible over time with a calm history and one next move.
Algorithm version
OS.Year1.v1.0
What counts now
Focus on the surfaces that prove the loop is real.
Auth and consent
Stand up the account state, route protection, and consent capture before anything clever.
Baseline experience
Make the first FFFrame loop understandable, resumable, and fast enough to complete in one sitting.
History and motion
Prepare the surfaces that will show snapshots, drift signals, and return-loop movement.
Pilot-ready evidence
Treat privacy, export, deletion, and operational proof as MVP features, not late polish.
Non-negotiables
MVP guardrails stay visible while the app is still small.
- FFFrame only. VVVantage and GGGravity stay out of this lane.
- Web Guide language stays human-first. Humans decide.
- No moral scoring and no therapist-replacement framing.
- Scoring remains server-only and never ships to the client bundle.
- Every visible AI output is clearly labeled AI-Suggested.
- Privacy, export, and deletion stay inside MVP scope.
Momentum from today
The repo has moved from generic scaffold to MVP-specific structure.
Landing surface
The default Next page is replaced with an MVP-specific front door.
Route scaffolds
Dashboard, baseline, and history previews now exist as concrete app surfaces.
Server-only core
Scoring and prompt-template skeletons are separated into their own server modules.
Supabase hooks
Browser and server helper entrypoints are in place for auth and data wiring.