The SA layer starts with local communities, councils and bioregions, then uses state machinery as a coordination layer. The default drill-down should be local councils, with switchable lenses for state electorates, bioregions and First Nations nation or language maps.
Last research run2026-05-08Australia/Brisbane
What belongs here
The map and tool layer.
Architecture is where SA decides how people move between community groups, councils, electorates, bioregions, protocol maps, public assets, local projects, public profile files, C-Hour contribution records, ledgers and simulations.
It should show what data exists, what is missing, what can be updated from markdown, and which map lens is currently active.
Not the constitution
Rules come next.
The constitution builder decides powers, limits, amendment pathways and legal commitments. This page designs the civic container those rules plug into.
The first proper state map should be clickable local councils. Electorates, bioregions and First Nations maps sit beside it as overlays, not replacements.
SA
Local councils layer
Future SVG or GeoJSON council boundaries should render here first, then each council opens its own self-similar local portal.
Map data target: assets/maps/sa-councils.svg or content/local-councils/sa.md
Local councils first
Default drill-down: local government areas, wards where relevant, public assets, local laws, rates, grants, services, council meetings, local project boards, public/private markdown streams and C-Hour eligible contribution categories.
Each council gets a portal, local ledger, local law memory, public noticeboard, public profile pattern and project board.
Each council should eventually show care, repair, disaster response, mentoring, ecological work and civic service records only where consent and verification are clear.
The state architecture should feel familiar without pretending every jurisdiction has the same laws, chambers, local government structure or cultural geography.
01
Overview
Capital, current government, chamber type, council count, map sources, maintainers and last research run.
02
Map stack
Councils, wards, electorates, bioregions, First Nations maps, public assets and disaster-risk overlays.
03
Tool stack
Local portals, public profile.md files, self-sovereign digital twins, ledgers, Legal RAG references, project boards, civic surges, election clocks and simulation hooks.
04
Braided economy
C-Hour categories, verification rules, reciprocity ledgers and local public-good contribution need to sit inside the state architecture from the start.
05
Public-private streams
Public noticeboards and contribution leaderboards can be agent-readable markdown, while private notes, identity material and sensitive care context stay out of public views by default.
06
Digital twins
A diary, photo album and filing cabinet are analogue twins; profile.md suites are lightweight digital twins; Aura Genesis is one deeper pathway, not the only doorway.
Agent-ready data
This builder needs its own markdown suite.
Current state facts come from content/states/sa.md. The next data layer should add council, electorate, bioregion, First Nations/protocol, public profile, public noticeboard, self-sovereign digital twin and contribution ledger markdown files so authorised agents can refresh maps without touching templates.
The 2026 election and Legislative Council declaration were checked against ECSA result sources. House totals are derived from ECSA final district data.