#, ## and ### help humans and agents see what belongs together.
Plain files for AI
Markdown with AI
For newcomers: a .md file is just a plain text note with headings. P4A uses it so people, groups and authorised agents can share context without losing control of privacy, sources, consent or review.
Source family
How to Use Markdown with AI
Adapted into P4A format from the external plain-English guide and the P4A civic builder suite. This page is orientation, not a data-upload service.
Beginner shape
A readable file before a clever tool.
Markdown is useful because it is boring in the best way. It is ordinary text, plus simple headings, lists, links and optional metadata. You can read it before an AI touches it, and you can inspect it after an agent uses it.
That matters for politics and civic work because a confusing form can become hidden power. A readable file lets people see what is being claimed, what is private, what has a source, what is still a guess and what needs human review.
Small frontmatter blocks can mark visibility, review status, dates, source type and confidence.
Source links, file names and dates help agents check before they sound confident.
Open questions and correction notes make the file safer to reuse later.
P4A lanes
Private life and public promises need different lanes.
The same file habit works at different scales. L0 can be a private note for self, home or household context. L1 can be a trusted local crew note. L2 can be a public front for a council, project, noticeboard or regional record. L3+ can be state, national, international or global coordination.
The rule is simple: people keep authority over private context, and public power leaves receipts. Agents can use files to draft, sort, compare and prepare actions, but changing the record is a permissioned step.
Identity, care, home, draft strategy, personal notes and private support context stay controlled by the record holder.
Groups, clubs, projects, families, crews and care circles can use working files with agreed boundaries.
Noticeboards, ledgers, source trails and project updates need review status, source links and correction paths.
State, national and global layers should be fed by local proof, not by vague claims dropped from above.
Six questions
Write the note before asking the model.
A useful Markdown file slows the work down just enough to stop the machine guessing. Before using AI, answer the basic questions in plain language.
What is this file for: a profile, notice, source trail, project brief, receipt, decision note or prompt packet?
What background would save a human from asking the first five obvious questions?
What is private, trusted-only, public, draft, uncertain or never for publication?
What useful next action should the AI help with right now?
Which links, dates, files, photos, meeting notes or official records should be checked?
Who reviews this, what is still unknown, and how should mistakes be corrected?
Agent use
The file is context, not surrender.
In P4A, a Markdown file can tell an authorised agent what it may read, what it may do, and where it must pause. That is different from giving the agent a blank cheque to edit, publish or merge records.
A good file can support reminders, drafts, translations, source checks, public summaries, project handovers, legal source trails, contribution notes and simulation prompts. The person or group still keeps the final say.
The agent can understand the file and prepare work inside the stated purpose.
The agent can make a draft notice, summary, source list, prompt packet or next-step plan.
Publishing, editing, sharing sensitive details or changing the record needs a human checkpoint.
P4A file examples
Small files can hold big governance habits.
P4A builders create local browser drafts. Downloading a file does not publish it. It gives a person or group a readable record they can inspect before asking an AI or another human to help.
L0profile.md
A private civic profile seed for roles, skills, boundaries, consent scope and review status.
L1public_noticeboard.mdA public or shared noticeboard contract with source trails, exclusions and correction paths.
L1-L2project-readiness.mdA project preparation file for purpose, eligibility, evidence, budget notes and permissions.
Lawlegal-source-trail.mdA source-first legal memory starter for jurisdiction notes, risk questions and human review.
Ledgercontribution-ledger-summary.mdA fractal contribution summary for money, care, repair, volunteering and correction paths.
Twinsensorium-place-pack.mdA place-twin source pack for local knowledge, risk, infrastructure and public summaries.
External guide
Open the fuller Markdown guide.
The cards below leave P4A and open the separate How to Use Markdown with AI site or source repo. Use that site when someone needs the slow beginner version, the browser-local starter builder, the civic-lanes explainer or the underlying repo.
Leaves P4AGuide home
The plain-English doorway for why Markdown helps people, groups and agents work with clearer context.
Leaves P4AStep-by-step guideThe longer explanation of purpose, context, boundaries, requests, sources and review notes.
Leaves P4AStarter file builderA separate browser-local builder for generating a simple AI context starter file.
Leaves P4AGitHub repoThe source repo for the guide, pages and builder.