Skip to main content
GitHub branch discipline protects Lucia from accidental environment drift.

​
Current GitHub Organization

Repositories: 
hello-lucia/lucia-admin
hello-lucia/lucia-booking-engine
Current local workspaces: 
Engine: engine-v0.1.3.6
Admin: admin-v0.1.3.6
Canon: lucia-vault-sync/HelloLucia.ai

​
Branches

Current working branches: 
dev
stage

​
Intended Flow

develop on dev
test in Development
capture Eval Labs dev baseline
review Eval Labs baseline
promote to stage
deploy Staging
smoke test
v0.1.3.6 must not be promoted to Staging until the Eval Labs Development baseline has been captured and reviewed.

​
Development CI Gate

Admin Dev CI exists and must pass: 
npm ci
npm run lint
npm run build
Admin Development deploys after checks pass. Engine Development truth for v0.1.3.6: 
branch: dev
GPT-5.5 default model
Responses API JSON gateway
semantic conversational intent assist live in Focus Ops
active_context from Signal Stream Chat live in Focus Ops
prior recommendation memory live in Focus Ops
workspace context awareness live in Development
saved DAW workflow awareness live in Development
real reminder persistence live in Engine
build identity exposed on Engine GET /
strict brain quality eval reached 178/178 after workspace-context awareness
Stripe sandbox payment foundation live in Development
durable Stripe financial ledger live in Development
Stripe financial truth wired into attention suppression
payment status routes preserved
Admin Development truth for v0.1.3.6: 
branch: dev
Calendar monthly booking spine live in Development
Lucia Workspace Sidebar Mode live in Development
shared Focus Ops conversation across Dashboard embedded mode and Workspace Sidebar mode
Workspace remains open across route changes
Calendar route is /calendar
Calendar reads /admin/bookings
Calendar booking clicks route to /bookings/:bookingId
live-dev topbar displays Admin and Engine build identity
Admin build identity is injected at build time
Engine build identity is fetched live from Engine root endpoint
build identity tag is runtime evidence for the current deployed pair
read-only /payments durable ledger page live in Development
read-only Booking Payment Truth card live on /bookings/:bookingId
Admin-only Payment Policy Baseline v0 visible on /property as policy draft / no persistence
payment DAW can open reconciliation context without mutating payment state
Payment truth commit chain recorded for source-truth traceability: Engine: 
e8427ec39b9e2132ec423a58545af4d3d3a4fd1c - feat: add stripe sandbox payment foundation
eea713127cb47db0ea99294f52ffd9378d01fc25 - feat: wire stripe financial truth into attention
35cee2415bb020a59c52a5700041ce6a509f8c22 - fix: harden financial truth wording
162f7d9a6844d8f60e9744b5a7eb7795bc2ed799 - feat: add stripe payment records index
88a09a1cfe37bdfcaf44723821a86155a849c63c - feat: add durable stripe financial ledger
Admin: 
a7367ace42860c620e260fd20d18713545447f57 - feat: add read-only payments page
c32a97056b74b8aaf82a4c8d31959e60a02d2351 - feat: add booking payment truth card
7c9683a37c89dc95a2c673a7603825d3c82fb77b - feat: add property payment policy baseline

​
Stage Protection

Stage should be protected with: 
PR required
no direct pushes
at least one approval when appropriate

​
Local Prompt Safety

Local terminal prompt should show current branch. This reduces accidental work on the wrong branch.

​
Canon Rule

When documenting a change, specify: 
repo
branch
environment
runtime layer
validation target

​
See Also