ACT constitution builder
The ACT constitution builder is not the national party constitution. It is a rulebook layer that should grow from local communities, councils and bioregions before it reaches state machinery: constitutional Acts, parliamentary structure, amendment paths, local government powers, democratic checks and what a future cyber-republic rehearsal would need to respect.
What belongs here
This page should explain the ACT constitutional machinery in plain English while staying rooted in the layers below it: community charters, council powers, public/private markdown rules, contribution ledger rules, parliament, executive government, courts and tribunals where relevant, electoral law, rights instruments if any, and how reform can lawfully happen.
Architecture link
The architecture builder handles communities, councils, electorates, bioregions, profile streams, public ledgers and map layers. This page handles what is binding, amendable, enforceable or only a proposal.
State-specific rule suite
Every state and territory needs a constitution page, but the content must respect local charters and actual legal machinery rather than pretending the state is the first layer.
Identify the constitutional Act, self-government Act or equivalent source of authority, with citations and plain-language notes.
Explain chambers, ministries, Governor or Administrator roles, confidence, committees and scrutiny pathways.
Show what can change by ordinary law, what needs referendum or special process, and what belongs to Commonwealth law.
Connect councils to the state constitution, local government Acts, planning schemes, rates, public assets and local laws.
Map rights instruments, integrity bodies, ombudsman, audit offices, anti-corruption bodies, courts and human review.
Use simulations and version-controlled drafts before proposing legal change, so people can inspect consequences first.
Separate verified public-good contribution from financial products, speculation and custodial crypto before any local pilot is proposed.
Define verification, consent, anti-fraud review, local redemption, public ledger records and human governance before C-Hours touch real councils or assets.
Define what a public profile.md can show, what requires opt-in consent, what stays private and how contributors correct or withdraw public records.
Let communities recognise useful work across money and C-Hours without turning care, identity or private life into a coercive score.
Braided economy foundation
The ACT constitution builder should track what would be needed for a C-Hour or Community-Hour pilot: local government authority, state legislative limits, financial services boundaries, public-purpose verification, non-speculative design and community-level consent rules.
Legal memory hook
The Legal RAG layer should hold the relevant Acts, regulator guidance, public-token arguments, council powers and state-local boundaries before any proposal claims it can operate.
Gamification line
Public noticeboards, profile.md files and community contribution leaderboards can help ACT communities see useful work, but the rules must separate public recognition from private context, identity data, care records and sensitive financial detail.
Process compatibility
Aura Genesis can inform the profile, ledger and contribution workflow as one intensive self-sovereign digital-twin pathway, including many .md files from a 60 by 2-hour HBOT-chamber practice. It is not exclusive: councils, bioregions and community groups should be able to build lighter markdown twins, rename, fork, simplify or replace the process while keeping the same public/private safeguards.
Current data
Current political and chamber data comes from content/states/act.md. The constitution builder should later get its own source file at content/constitutions/act.md.
Current members, party breakdown and end-of-term date were checked against ACT Legislative Assembly and Elections ACT sources.
Builder warning
This page is a civic literacy and drafting workbench. It should not present proposals as law, legal advice or adopted policy. Every claim needs sources, version history and room for correction.