Experience 003 · The Ubuntu Town Operating System · Blueprint is portfolio authority · Supabase is operational truth · nothing fabricated

Your world

GOOD MORNING.
HERE IS WHAT MATTERS NOW.

Role

Public visitor — no role assigned to this session

Role assignments are protected records. No role is assumed and no permission is implied.

Scope

Public operating layer

50 Blueprint towns · 9 provinces · 10 canonical initiatives · database coverage: 81 canonical rows

What matters now

4 canonical initiatives need portfolio reconciliation

Computed from the registry reconciliation — a governance decision awaits a human.

Needs attention

COMPUTED

Decision required

Portfolio reconciliation (C-01): Daycare/DaycareOS and Ubuntu Socials/Buntu Bar remain UNRESOLVED; 2 database rows are portfolio-unreconciled.

Why: registry reconciliation against live catalog rows. Evidence: public.initiatives (12 rows) vs canonical ten. A Supabase row does not become canonical by existing.

open the portfolio →

Ownership gap

Initiative heads and town coordinators are unconfirmed across the portfolio — every ownership slot renders as an interim vacancy.

Why: no accessible person/role records (RECORDS NOT ACCESSIBLE). Placeholders are operating objects with next actions — never invented people.

open People & Capability →

Proof gap

Field intelligence defines proof requirements (49 standards) but no captured proof is accessible.

Why: workpack proof_required lists are real research artefacts; captured proofs are protected records. PROOF GAP — not failure, not zero.

open My Work →

What changed

COMPUTED

0 town record(s) touched in the last 30 days (COMPUTED from updated_at). CHANGE HISTORY NOT YET AVAILABLE: what changed inside each record cannot be reconstructed without history records — this system will not manufacture a delta from a timestamp.

CHANGE HISTORY NOT YET AVAILABLE at object level — this system will not manufacture a delta from a timestamp.

What did I learn

Learning feed

ABSENT

ABSENT — uto.learnings does not exist in the canonical schema (verified). The learning step of the operating loop is a documented structural gap (G3): completed work can be proven but cannot yet be recorded as learning. Memories (protected) hold narrative context for authorised users. Until the learnings object exists, this system shows the gap — never a fake learning feed.

What should happen next

DERIVED

Conduct a market research survey to identify logistics and community needs.

From: Town Opportunity Scan (Bethlehem) — research-derived guidance, not an assignment.

Open this work item →

Your work

DERIVED
  • Town Opportunity Scan

    To identify and prioritize opportunities for economic growth and service enhancement.

    Bethlehem · Field intelligence Dihlabeng_Local_Municipality_Bethlehem · priority high · proof required: market_research, stakeholder_feedback

  • Community Podcast Capture

    To engage the community and gather insights through podcast content.

    Bethlehem · Field intelligence Dihlabeng_Local_Municipality_Bethlehem · priority medium · proof required: podcast_transcripts, listener_engagement_data

  • Youth CV Activation

    To provide job readiness training and job placement services for youth.

    Bloemfontein · Field intelligence MAN_Bloemfontein_v1 · priority high · proof required: job market analysis, youth employment statistics

  • Community Podcast Capture

    To engage the community through podcast content that highlights local issues and solutions.

    Bloemfontein · Field intelligence MAN_Bloemfontein_v1 · priority medium · proof required: community interest survey, podcast hosting platform

  • Town Opportunity Scan

    To identify and document existing and potential economic opportunities in the town.

    Bloemfontein · Field intelligence MAN_Bloemfontein_v1 · priority low · proof required: local business directory, economic development report

Assigned work

Work assigned to you by a person: RECORDS NOT ACCESSIBLE. Assignment records are protected in the canonical system. The queue above is DERIVED from real field-intelligence workpack recommendations — it is guidance, not assignment.

Your development

Capability, coaching and 30/60/90 outcomes require authorised people-system evidence — RECORDS NOT ACCESSIBLE. The People & Capability layer refuses to invent assessments.

open People & Capability →

Your towns

Your initiatives

What changed?

Last 30 days: 0 canonical town record(s) created, 0 updated (window: rolling 30 days · source: uto.towns timestamps).

COMPUTED

Change history for operational objects: CHANGE HISTORY NOT AVAILABLE — no prior-state store exists and operational records are protected. No delta is manufactured.

CHIEF OF STAFF

operating intelligence · Home · your world

What is happening?

The network is represented by 81 canonical database town rows across 9 provinces — the Blueprint cohort is 50 towns, a distinct designation.

COMPUTED
Why?

Evidence: uto.towns (live read) · Blueprint cohort law

Reasoning: Row count and province grouping computed from the canonical geography source.

Limitation: CANONICAL BLUEPRINT (50) ≠ CANONICAL DATABASE (81 rows) ≠ OPERATIONAL COVERAGE. The three are never conflated.

6 of the 10 canonical initiatives have a linked database record; 1 possible match is unresolved; 3 are database-absent; 2 database rows are portfolio-unreconciled.

COMPUTED
Why?

Evidence: public.initiatives (live read) · Canonical registry (Blueprint)

Reasoning: Registry reconciliation classification per the data law.

Limitation: This is a governance state, not a defect count. Human decision required (C-01).

PROPOSED — PENDING HUMAN APPROVAL: Ratify the portfolio reconciliation: resolve Daycare/DaycareOS and Ubuntu Socials/Buntu Bar, and decide the fate of the database-only rows.

50 canonical rows carry the is_founding flag, and 9 towns carry field-intelligence packs.

COMPUTED
Why?

Evidence: uto.towns.is_founding · field-intelligence packs (v1 exports)

Reasoning: Counts of flagged rows and available packs.

Limitation: The is_founding flag derives from the Founding-50 reconciliation migration — it is NOT the ratified Blueprint roster (roster RATIFIED 2026-10-21, v1.1.0-ratified).