P4APurple Partyfor Australia
Builder suite These tools run in the browser and create local Markdown files. They do not submit data, create accounts or publish anything by themselves. Architecture link Markdown with AI External guide Field kit Ledger
Purple civic map used as the P4A builder suite background

L0 / L1 / L2 / L3 practical layer

Civic Twin Builders

Start with readable files before heavy platforms. These small builders turn P4A's roots-up governance pattern into local Markdown records that humans can inspect and authorised agents can use for user-approved actions. Editing those records is a separate permissioned workflow.

Open the suite See the architecture Markdown with AI
L0 self, home, private twin L1 local mesh, crew, group L2 council, region, public front L3+ state, national, international, global

Builder suite

Private first, public by consent.

The suite demonstrates the grassroots development path: L0 is self/home, L1 is local mesh, L2 is regional or civic front, and L3+ is macro scale such as state, national, international or global. The tools are fractal: a noticeboard, ledger or milestone can be private, shared or public depending on consent and scale. Most tools create local Markdown drafts that agents may use for approved actions. Changing the records is a later permissioned container, not the default right of an agent.

Lane 1

Private civic note to chosen public edge

For people starting privately: create only the civic notes needed for P4A work, then decide what, if anything, can become an opt-in public contribution edge.

Some L0 records are deliberately not built here. Deep personal AI, Aura Genesis, health, memoir, household sensor or intimate support records belong outside the P4A builder suite. This page only offers light civic records that can help people organise, contribute, review and consent. Aura Genesis context
L0

Private Civic Profile

Create a private profile.md seed for identity, roles, skills, consent scope and public/private boundaries.

 L0

Private Noticeboard

Make a private board for self, home, study, care, health, repairs, habits or any life area the owner wants to improve.

 L0-L1

Contributor Card

Prepare an opt-in public summary of roles, offers, skills and contribution references without exposing private proof.

Lane 2

Local work to reviewed evidence

For crews, projects and campaigns: move from handover and public coordination into readiness, source checks, assets, milestones and contribution summaries.

L1

Local Crew Onboarding

Turn a table, event, market, care circle or project crew into a readable handover file.

 L1-L3

Public Noticeboard

Define a shared or public noticeboard, boundary, reviewer, notice types, private exclusions and correction path.

 L1-L2

Project Readiness

Collect purpose, eligibility, evidence, budget notes, permissions and community benefit before a project goes public.

 L0-L2

Legal Source Trail

Prepare source lists, jurisdiction notes, risk questions, evidence and human-review prompts for Legal RAG.

 L1-L2

Media Assets

Record asset lists, provenance, licences, shared gear, AI-use notes and approval status.

 L1-L2

Milestone Report

Summarise public-benefit progress, receipts, blockers, human review and next steps.

Lane 3

Place node to living boundary

For home, place, ecology and infrastructure context: keep private place records local first, then only widen into place packs and living boundaries by consent and authority.

L0

Sovereign Space Node

Start a private place-node record for home context, environmental twin hints, consent and mesh-sync limits.

 L1-L2

Sensorium Place Pack

Bundle local place knowledge, ecological context, infrastructure notes, risks and public summaries.

 L2

Living Boundary Map

Frame the civic boundary as a living island, catchment, bioregion, disaster corridor or food system.

 Leaves P4A

Straddie Digital Twin Builders

External example for turning rooms, places and bioregions into Markdown prompt packets for visual and world-building tools.

Convergence

Reviewed civic scale

The lanes meet where contribution evidence, C-Hour receipt design and local civic front architecture need stronger authority, human checkpoints and correction paths.

L0-L3

Contribution Ledger Summary

Draft private, shared or public contribution summaries for money, time, evidence and correction paths without minting C-Hours.

 Future

C-Hour Receipt Pipeline

Design the agent-generated Markdown/blockchain receipt lane: accepted authority, source data, legal gates, human review and correction path.

 L2

Local Civic Front

Connect local projects, noticeboards, ledger summaries, legal sources and human review into one civic doorway.

Public/private boundary

Markdown is the contract, not the permission.

A generated file is only a draft. Private files stay private. Permissioned files need the named people to understand the use. Public files need source trails, review status and correction paths before they become part of any ledger, noticeboard or digital twin.

L0 privateHome, identity, private notes, care context and optional public summary rules.
L1 local meshCommunity pages, noticeboards, project records and shared review habits.
L2 civic frontCouncil, electorate or public-good ledgers only after local proof and human review.

Markdown with AI

New to .md files? Start with the P4A version.

The P4A Markdown page gives the quick local explanation: what a .md file is, why agents can use it, and why private context, public notices, source trails and corrections belong in different lanes. The external guide goes slower for beginners and includes its own starter builder.

Open P4A page External guide GitHub repo
Back to architecture Open field kit Start at L0