Audit map doctrine boundaries

This commit is contained in:
Meta Vens 2026-04-26 04:57:30 +01:00
commit e44de5793b
6 changed files with 76 additions and 0 deletions

View file

@ -1,5 +1,21 @@
# Repixelizer Hosted Auth Architecture
## What this file is
This file is a future architecture note for hosted-demo authentication and
entitlement work.
It is not a map of code that already exists in the repo. Current live hosted
demo behavior is still just:
- hosted-demo runtime limits and UI flags in `src/repixelizer/gui.py`
- the local single-process queue in `src/repixelizer/gui.py`
- frontend consumption of `hostedDemo` runtime config in `frontend/src/app.ts`
If future auth work lands and this note drifts away from the code, trust the
code first and either update this document or cut the stale parts instead of
pretending the architecture already exists.
## Summary
The hosted Repixelizer demo should support both:
@ -405,3 +421,21 @@ Keep these sacred:
- linking identities must never merge two existing local users implicitly
If we violate those rules, the auth system will become a damp little pit of edge cases almost immediately.
## Audit Result
This design is still compatible with the current Epiphany workflow after one
important correction: it must be treated as future architecture, not current
truth.
That boundary is now explicit. The note can keep its job if it stays focused on:
- the proposed local-user plus linked-identity model
- the `discord_allowed || patreon_allowed` entitlement rule
- the implementation phases and invariants for future auth work
It should not quietly become:
- a handoff note
- a claim that auth is already landed
- a duplicate of the live queue behavior already described by the code

View file

@ -1,5 +1,16 @@
# Repixelizer Implementation Plan
## What this file is
This file is the forward plan and active hypothesis ledger for Repixelizer.
It is not the authoritative stage-by-stage control-flow map. That lives in
`docs/lean-optimizer-algorithm-map.md`.
If these two notes disagree about what the code does right now, trust the
algorithm map and the source, then fix this plan instead of hand-waving about
intent.
## Current machine
Repixelizer now has one live reconstruction engine:

View file

@ -566,3 +566,28 @@ These are the categories of complexity that would change the nature of the solve
- repeated structural score families that appear in more than one stage
The whole point of this machine is that it stays one field, one loss, one final sample.
## Audit Result
This map is compatible with the current Epiphany workflow as long as it keeps
doing one job: describing the live machine the repo actually runs.
Right now it passes that test:
- it names the current pipeline instead of a future fantasy machine
- it anchors every stage to real source files
- it keeps the prose explanation attached to the control flow instead of
replacing it
- it identifies the current seams and the forbidden complexity that would turn
the solver back into a Jenga tower
The important boundary is simple:
- live control-flow truth belongs here
- active hypotheses and next cuts belong in `docs/implementation-plan.md`
- compact re-entry instructions belong in `notes/fresh-workspace-handoff.md`
- durable project truth belongs in `state/map.yaml`
If a future pass adds directional edge awareness, anisotropic behavior, or
another real control-flow change, update this map after the code lands. If the
change is still a hypothesis, keep it out of this file.