LivingRegister federation hubHub federato LivingRegister
Technical register view for canonical people data, member-register projections, task/calendar bridge state, contract gates, and dashboard navigation. This page exposes aggregate state only: no documents, phone numbers, emails, or unapproved personal records.Vista tecnica del registro per dati canonici sulle persone, proiezioni dei registri membri, stato del ponte task/calendario, controlli contrattuali e navigazione tra dashboard. Questa pagina espone solo dati aggregati: nessun documento, telefono, email o record personale non approvato.
Total unified records.
People still in application or evaluation.
People currently treated as residents by the register.
Active or signed Membership Agreement rows.
Known room and space records.
Spaces marked occupied or assigned.
Private-area identities with mandatory email and phone.
Comprehensive application-form answer records.
Calendar Register events in the core database.
Calendar rows still in the upcoming bucket.
Events allowed for website-facing display.
Signed-document residency stays allowed into calendar views.
Stay rows blocked from calendar publication.
Task Register rows materialized into the LivingRegister core.
Tasks not completed and not draft.
Completed Task Register rows.
Task dates projected into Calendar Register markers.
Teams currently represented in the Task Register.
People, contracts, spaces, stays, auth, task/calendar projections.
Candidate RegistermemberApplication and candidate pipeline surface.
Resident RegistermemberResidents and signed stay windows projected into canonical people state.
Task RegistermemberOperational team work, dependencies, due dates, and AI task planning.
Calendar RegistermemberPublic events, private planning events, residency stays, and task markers.
House RegistermemberRooms, spaces, occupancy, and spatial projections.
Bureau RegistermemberLaTeX contracts, signed-copy gates, Drive/legal archive references.
Financial RegisterexternalIndependent finance register receiving only approved LivingRegister facts.
Weather RegisterexternalIndependent weather context for planning and event decisions.
People data: one canonical identity layer lives in lr_people and person-scoped satellite tables.
Task data: tasks remain an independent register and project dates into core_task_calendar_markers.
Finance data: the Financial Register is not absorbed into LivingRegister; only approved outbox/projection data may cross that boundary.