AI Garden Work

AI Garden Work names the AI-facing protocol for proposing Atlas changes through the Atlas Garden rather than directly rewriting canonical Atlas content.

It gives an AI participant a bounded way to help tend the Atlas. The AI reads through the MCP, traces the relevant entry, names one small care movement, writes a Garden proposal, and stops. The proposal can then be reviewed, lit, shaded, approved, seasoned, applied, or left waiting.

AI Garden Work is not authorship, grounding, or direct correction. It is participation under garden conditions.

Places

AI Garden Work places the AI-facing protocol for proposing Atlas changes through the Garden rather than directly rewriting canonical Atlas content.

Holds

AI Garden Work is held by AI Participation, Atlas Garden, Garden Pass, Atlas Note Standard, and Check.

AI Participation constrains the participant mode. Atlas Garden holds the proposal space. Garden Pass limits the work to one tended movement. Atlas Note Standard preserves note form. Check keeps the proposal answerable.

Pairs

AI Garden Work pairs with direct edit.

Direct edit changes canonical content immediately. AI Garden Work plants a proposed change where it can be reviewed, seasoned, lit, shaded, approved, or left waiting.

Traces

• AI Participation
• Atlas Garden
• Garden Pass
• Atlas Note Standard
• Check
• Carry-Trace Test

Nests

AI Garden Work nests inside Atlas Garden as the AI-specific way of doing Garden work through MCP reading and Garden proposal writing.

The ordinary movement is:

1. Read the AI entry protocol.
2. Search only to find an entry point.
3. Read the target entry.
4. Read related structure before making an Atlas claim.
5. Choose one small care movement.
6. Write one Garden proposal.
7. Stop.

Reads

AI Garden Work becomes recognisable where an AI participant wants to help tend the Atlas by reading with the MCP, tracing the target entry, naming one small proposed change, and using the Garden rather than treating its output as canonical.

The AI should use Garden proposals for:

clean-pass      small readability, repetition, or section-shape cleanups
thin-section    a section that needs more carrying or clearer placement
alignment       mismatch between note structure and prose
drift           language or implication that moves beyond its trace
reciprocity     carry/trace relation that needs checking

The AI must not use AI Garden Work to ground entries, invent terms, bypass review, collapse Atlas order, rename concepts, merge entries, or apply unreviewed rewrites.

A Garden proposal should stay small:

one entry
one issue
one section if possible
one public summary
one proposed change
one trace/check reason

The Garden proposal fields are:

entry_id             the Atlas entry being tended
kind                 reciprocity, thin-section, alignment, drift, or clean-pass
confidence           high, medium, or low
summary              one short public-facing sentence
proposed_changes     the proposed change, preferably naming the section
reciprocity_issues   what relation, carrying, or check issue is touched; otherwise None

If the AI is uncertain, it should lower confidence, name the uncertainty, or wait. Waiting is a valid care action.

Carries

• Garden Pass
• Garden Status
• AI Participation