atris 3.58.7 → 3.59.0

package/AGENTS.md

@@ -171,8 +171,9 @@ named none. These rules are the difference, in priority order:
 7. **Final report = files changed + verify command + its exact exit/output.**
    Judges read the worktree diff, not your prose; an empty report with a clean
    diff beats a confident report with no diff.
-8. **Update `atris/MAP.md` sections you touched** (file:line refs drift on
-   their own clock; stale refs contradict closed lessons for months).
+8. **Update the map sections you touched:** routing rows in `atris/MAP.md`,
+   file:line refs in `atris/refs/MAP-NOTES.md` (refs drift on their own clock;
+   stale refs contradict closed lessons for months).
 9. **Real runtime over mocks:** if you fixed live behavior, the regression test
    reproduces it against the real runtime, not a mock that can stay green
    through breakage.

package/GETTING_STARTED.md

@@ -1,6 +1,6 @@
 # Getting Started with Atris
 
-Atris turns any folder into a workspace that gets better over time. Integrates with any agent.
+Atris turns any folder into a workspace that gets better over time. It works with any coding agent.
 
 ## Install
 
@@ -71,7 +71,7 @@ In your coding agent, say `/endgame` or describe where you want to end up. The s
 atris autopilot --auto --iterations=5
 ```
 
-Or in your coding agent, say `/loop` to schedule it to run every ~15 minutes.
+Or in your coding agent, say `/loop` to schedule it every 13 minutes.
 
 The loop runs until the goal is done, then picks the next one from scorecards + inbox.
 

package/PERSONA.md

@@ -1,4 +1,4 @@
-# PERSONA.md — Atris Agent Personality
+# PERSONA.md: Atris Agent Personality
 
 This defines how Atris agents communicate, decide, and work.
 
@@ -28,21 +28,17 @@ This defines how Atris agents communicate, decide, and work.
 
 ## Core Workflow
 
-**Read before you act.** Before planning or building, read the relevant files. Understand the current state. Your first action in any new area is always reconnaissance — not execution.
+**Read before you act.** Before planning or building, read the relevant files. Understand the current state. Your first action in any new area is always reconnaissance, not execution.
 
-**Always ask for intent.** Clarify before acting.
+**Ask for intent when it's fuzzy or the blast radius is real.** A vague brief gets 2-3 named interpretations with a recommendation, not open questions. Small, reversible, clearly-scoped work: act, then report. Standing autonomy (autoland, push-asap) means asking permission for routine work is a failure smell, not politeness.
 
-**Use ASCII visualization to confirm understanding:**
+**Use ASCII visualization to confirm understanding when a plan is worth confirming:**
 - **UI elements:** Show design using ASCII
 - **Backend:** Use arrows, diagrams, logic gates
 - **Databases:** Tables and graphs showing relationships
 - **Other cases:** Use best judgment
 
-**Always confirm understanding in ASCII visualization layer for planning.**
-
-Then go 3-4 sentences one by one through each task.
-
-Once every task is confirmed, create a plan.
+A one-file fix needs no diagram; a new surface or cross-system change does.
 
 **If a task is too big, break it down.** One job per task. If you can't describe "done" in one sentence, decompose it. Small precise tasks compound into big results.
 
@@ -56,9 +52,13 @@ We can always add layer by layer.
 
 ## Communication Style
 
-**3-4 sentences max.** No verbose explanations. Get to the point.
+**Talk like a person.** Every message the operator reads: plain words, what happened and what it means for them, cause and effect. Not the machinery.
+
+**No codes in the message body.** No task ids, branch names, commit hashes, PR numbers, or system nouns (worktree, verifier, projection, tick). If the reader needs a command, ONE copyable line at the end. Insider terms get defined in the same breath or cut.
+
+**Lead with the outcome.** Complete sentences, one or two per paragraph, blank line between. No headers, bullet stacks, or tables in chat replies. Detail lives in files; offer "want the detail?" instead of dumping it.
 
-Direct and casual tone. No corporate speak.
+**The test before sending:** read it fried at 2am. If decoding takes work, rewrite it.
 
 If something is slop, call it out. Optimize ruthlessly.
 

package/README.md

@@ -260,7 +260,7 @@ atris business record atris/reports/2026-04-12-operator-recap.md --outcome mixed
 - `atris codex-goal` is the read-only bridge for native Codex `/goal`: `status` inspects the live goal database, while the legacy `reset` command now refuses every mutation. Active tasks continue in place; completed tasks retain their final goal, and new work or recurring monitors use a new dedicated Codex task.
 - `atris task` keeps durable local task state and append-only events for agents; `atris/TODO.md` is just a regenerated readable board. Run the loop with `atris task new`, `delegate "..." --to <owner>`, `next`, `say`, and `ready <id> --proof "..."`; human approval is `atris task accept <id>` (moves to Done, awards Career XP) or `revise <id> --note "..."`. Final task transitions also append the general daily log and, when a real `atris/team/<member>/MEMBER.md` matches the task owner, that member's daily log. Add `--json` for headless agents, `atris task serve` for the local board, and `atris task show <ref>` / `events --all` for the full ledger. Commands accept semantic refs (`OBL-18`), full IDs, or any unique prefix. In cloud business workspaces, Supabase `tasks` is the source of truth and Swarlo the live claim layer.
 - `atris mission` is the durable autonomy layer: start with an owner, verifier, runner, and stop condition; record bounded work with `mission tick`; close with `mission complete` only after proof. Runners include `manual`, `claude`, `atris2`, and `codex_goal`.
-- `atris pulse` is the OS-cron heartbeat for overnight self-improvement. Use `atris pulse status`, `tick`, `run`, `install --cadence "<cron>" --days 7 --verify "npm test" --model claude-opus-4-8`, and `uninstall`.
+- `atris pulse` is the OS-cron heartbeat for overnight self-improvement. Use `atris pulse status`, `tick`, `run`, `install --cadence "<cron>" --days 7 --verify "npm test" --model claude-opus-5-5`, and `uninstall`.
 - `atris experiments` runs small test packs in `atris/experiments/`
 - `atris pull` and `atris push` sync cloud workspaces and journals
 - `atris live` keeps a business brain fresh by checking/fixing the workspace, pushing local state, pulling cloud state, and pushing again after local changes go quiet

package/atris/GEMINI.md

@@ -1,8 +1,8 @@
-# GEMINI.md — Atris Project Instructions
+# GEMINI.md: Atris Project Instructions
 
 You are running inside **Atris**, an AI workspace operating system.
 
-## FIRST MESSAGE — Boot Sequence
+## FIRST MESSAGE: Boot Sequence
 
 **Before your first response, run this command and display its full output:**
 
@@ -27,10 +27,11 @@ This is the Atris boot sequence. Show the output to the user, then respond natur
 
 ## Core Files
 
-- `atris/MAP.md` — navigation (use file:line references)
-- `atris/TODO.md` — current work queue (target state = 0)
-- `atris/logs/YYYY/YYYY-MM-DD.md` — journal (Inbox + Completed)
-- `atris/atris.md` — protocol/spec
+- `atris/MAP.md`: navigation (use file:line references)
+- `atris task` - the source of truth for work: current tasks, claims, dialogue, and proof
+- `atris/TODO.md`: rendered/legacy task view only
+- `atris/logs/YYYY/YYYY-MM-DD.md`: journal (Inbox + Completed)
+- `atris/atris.md`: protocol/spec
 
 ## Default Loop
 

package/atris/PERSONA.md

@@ -6,7 +6,7 @@ This defines how Atris agents communicate, decide, and work.
 
 ## MAPFIRST (Non-Negotiable)
 
-**Before searching for ANYTHING in the codebase:**
+**Before searching for anything in the codebase:**
 
 ```
 1. READ atris/MAP.md first
@@ -20,7 +20,7 @@ This defines how Atris agents communicate, decide, and work.
 **Violations:**
 - ❌ Running grep/ripgrep before checking MAP.md
 - ❌ Searching multiple files when MAP.md has the answer
-- ❌ Finding something via grep and NOT updating MAP.md
+- ❌ Finding something via grep and not updating MAP.md
 
 **MAP.md is truth. Check it first. Always.**
 
@@ -86,7 +86,7 @@ Delete when done. Clean workspace = clear mind.
 
 ## Collaboration
 
-**Trust the system.** MAP.md is truth. TODO.md is current work (formerly `TODO.md`).
+**Trust the system.** MAP.md is truth. `atris task` is the source of truth for work; `TODO.md` is the rendered view.
 
 Navigator finds, executor builds, validator verifies. Stay in your lane.
 
@@ -112,7 +112,7 @@ Mistakes are fine if you learn and fix quickly.
 
 ❌ Make assumptions without checking MAP.md
 
-❌ Leave TODOs scattered in code (put them in TODO.md)
+❌ Leave TODOs scattered in code (put them in `atris task`)
 
 ❌ Overthink simple problems
 

package/atris/features/README.md

@@ -13,7 +13,8 @@ atris/features/
 ├── _templates/               # Templates for new features
 │   ├── idea.md.template      # Problem, solution, visualization
 │   ├── build.md.template     # Step-by-step build instructions
-│   └── validate.md.template  # Proof it works (or didn't)
+│   ├── validate.md.template  # Proof it works (or didn't)
+│   └── changelog.md.template # Release notes entry
 ├── feature-name-1/
 │   ├── idea.md               # Why we're building this
 │   ├── build.md              # How to build it
@@ -49,7 +50,7 @@ cp atris/features/_templates/validate.md.template atris/features/your-feature-na
 # Fill in the templates
 # Edit idea.md (problem, solution, visualization)
 # Edit build.md (step-by-step implementation)
-# Edit validate.md (proof it works — filled by validator)
+# Edit validate.md (proof it works, filled by validator)
 ```
 
 ---
@@ -68,7 +69,7 @@ cp atris/features/_templates/validate.md.template atris/features/your-feature-na
 3. Updates status as work progresses
 
 **Validator Agent (validate.md):**
-1. Fills in `validate.md` — runs every check, records pass/fail
+1. Fills in `validate.md`: runs every check, records pass/fail
 2. If all pass → status "complete", lessons learned to journal
 3. If any fail → status stays "in-progress", lessons learned to journal
 4. Updates MAP.md if needed
@@ -118,7 +119,7 @@ Local-first project wiki with cloud opt-in
 - **Completed:** 2026-04-07
 
 #### self-improving-loop
-Make Atris recursive — validate.md lessons feed back into the next idea.md
+Make Atris recursive: validate.md lessons feed back into the next idea.md
 - **Files:** atris/lessons.md (new), atris.md, atris/team/navigator/MEMBER.md, atris/team/validator/MEMBER.md, atris/MAP.md
 - **Status:** complete
 - **Keywords:** recursion, lessons, feedback-loop, self-improving, lessons.md
@@ -133,7 +134,7 @@ Connect lessons.md and validate.md to every CLI command and doc that references
 - **What:** 8 surgical edits to wire lessons.md and validate.md into init, plan, review, status, docs, and spec
 - **Completed:** 2026-02-09
 
-#### brainstorm — v2.0.0
+#### brainstorm: v2.0.0
 Conversational exploration mode for uncertain ideas
 - **Files:** bin/atris.js, atris/atris.md, atris/PERSONA.md, GETTING_STARTED.md, README.md, atris/MAP.md
 - **Status:** complete
@@ -142,7 +143,7 @@ Conversational exploration mode for uncertain ideas
 - **Why:** Users need supportive thinking partner when uncertain about requirements
 - **Completed:** 2025-11-11 (shipped in v2.0.0)
 
-#### cli-ux-simplification — v2.0.0
+#### cli-ux-simplification: v2.0.0
 Simplified CLI surface around the core workflow and aligned internal artifacts.
 - **Files:** bin/atris.js, commands/init.js, commands/workflow.js, commands/status.js, commands/brainstorm.js, lib/state-detection.js, atris.md, atris/atris.md, GETTING_STARTED.md, atris/GETTING_STARTED.md, AGENT.md, CLAUDE.md, atris/PERSONA.md, PERSONA.md
 - **Status:** complete
@@ -151,6 +152,76 @@ Simplified CLI surface around the core workflow and aligned internal artifacts.
 - **Why:** Makes it easier for humans and agents to understand and consistently use the CLI without memorizing many commands.
 - **Completed:** 2025-11-16
 
+#### cloud-sync-simplicity
+Make cloud sync's safe path the default: per-conflict review, orphan cleanup, scoped push
+- **Files:** commands/business-sync.js, commands/cloud.js, commands/push.js, commands/sync.js
+- **Status:** complete
+- **Keywords:** sync, cloud, conflicts, orphans, push
+- **What:** `atris sync --review` picks local/cloud/merge per conflicting file (`commands/business-sync.js:355`), `atris cloud clean` previews and deletes cloud orphans (`commands/cloud.js:22`), and push leads with the safe path on drift (`commands/push.js:349`)
+
+#### codex-goal-replacement
+Bridge Atris mission selection into the Codex visible goal
+- **Files:** commands/codex-goal.js, commands/mission.js, bin/atris.js
+- **Status:** complete
+- **Keywords:** codex, goal, mission, bridge
+- **What:** `atris codex-goal` writes `.atris/state/codex_goal.json` (schema `atris.codex_goal.v1`) so the Codex runtime can mirror `goal.visible_goal` into the native goal UI
+
+#### company-brain-sync
+Sync the atris/ brain surface of a business workspace instead of raw file mirroring
+- **Files:** lib/company-brain-sync.js, commands/business-sync.js, commands/sync.js
+- **Status:** complete
+- **Keywords:** sync, business, company-brain, workspace
+- **What:** `atris sync --status` renders business, brain file count, conflict packets, and watcher heartbeat without credentials
+
+#### pack-recovery
+Recover recorded pack file work after an interrupted run
+- **Files:** commands/pack.js
+- **Status:** complete
+- **Keywords:** pack, recover, recovery, protected-files
+- **What:** `atris pack run --recover <receipt.json>` marks completed files protected and continues the run (`commands/pack.js:166`, `:2536`)
+
+#### plan-review-by-validator
+Validator gate between plan and do so half-specified plans never execute
+- **Files:** commands/autopilot.js, test/autopilot-plan-review.test.js
+- **Status:** complete
+- **Keywords:** plan, review, validator, signoff
+- **What:** the validator reads each plan fresh and returns a machine-parseable SIGNOFF/REJECT verdict before execution (`commands/autopilot.js:1249-1510`)
+
+#### self-driving-mission
+Give Atris a destination once; it owns route, staffing, recovery, and the arrival receipt
+- **Files:** commands/mission.js, lib/runner-command.js, lib/fleet.js
+- **Status:** complete
+- **Keywords:** mission, self-driving, route, engine, autoland
+- **What:** `atris mission run` drives a durable objective with `--due`, `--max-ticks`, and `--complete-on-pass` (`commands/mission.js:581-641`)
+
+#### spaceship
+Bounded, self-reporting overnight runner
+- **Files:** commands/spaceship.js, scripts/spaceship.sh
+- **Status:** complete
+- **Keywords:** spaceship, overnight, runner, supervised-loop
+- **What:** `atris spaceship` wraps the supervised loop script that survives bad ticks and reports each state change
+
+#### team-member-standard
+MEMBER.md directory format for team members
+- **Files:** atris/team/*/MEMBER.md
+- **Status:** complete
+- **Keywords:** member, MEMBER.md, team, standard
+- **What:** every team member lives in `atris/team/<name>/MEMBER.md`; init and sync ship them into user projects (`commands/sync.js:526-531`)
+
+#### verify-falsifiability
+The Verify field must be a real rubric that fails before work and passes after
+- **Files:** commands/verify.js, commands/autopilot.js
+- **Status:** complete
+- **Keywords:** verify, falsifiable, rubric, reward
+- **What:** `atris verify` runs the task's rubric against the tree; a rubric that already passes halts the tick instead of counting a fake success
+
+---
+
+### Parked Features
+
+#### customer-skill-zones
+- **Status:** parked, partially shipped; private publish parked per `atris/features/customer-skill-zones/idea.md`
+
 ---
 
 ## Guidelines

package/atris/skills/README.md

@@ -6,8 +6,8 @@ Agent-agnostic skills. Works with Claude, Cursor, Codex, any LLM agent.
 
 Every process = **Skill + Policy**
 
-- `skills/[name]/SKILL.md` — How to DO (process)
-- `policies/[name].md` — How to REVIEW (validation)
+- `skills/[name]/SKILL.md`: How to DO (process)
+- `policies/[name].md`: How to REVIEW (validation)
 
 ## Integration
 
@@ -25,19 +25,46 @@ cp -r atris/skills/[name] ~/.codex/skills/
 
 | Skill | Description | Policy |
 |-------|-------------|--------|
-| atris | Workflow enforcement + plan/do/review | `policies/ANTISLOP.md` |
-| autopilot | PRD-driven autonomous execution | — |
-| autoresearch | Bounded keep/revert experiment loops via `atris/experiments/` | — |
-| backend | Backend architecture anti-patterns | `policies/atris-backend.md` |
+| aeo | Content engineered to get cited by ChatGPT, Claude, and Gemini | - |
+| apps | View, manage, and trigger Atris apps | - |
+| atris | Workspace navigation, tasks, MAP.md, where-is-X questions | `policies/ANTISLOP.md` |
+| atris-feedback | Submit, list, resolve, close, or delete customer feedback | - |
+| autopilot | Run one autonomous plan/do/review tick | - |
+| autoresearch | Keep/revert experiment loop for experiment packs | - |
+| backend | Backend architecture policy | `policies/atris-backend.md` |
+| blocks | Author Atris block documents: docs, decks, reports | - |
+| calendar | Google Calendar via AtrisOS API | - |
+| copy-editor | Detects and fixes AI writing patterns | - |
+| create-app | Build and deploy an Atris app from a description | - |
+| create-member | Create and manage MEMBER.md team members | - |
 | design | Frontend aesthetics policy | `policies/atris-design.md` |
-| calendar | Google Calendar integration via AtrisOS | — |
-| drive | Google Drive + Sheets integration via AtrisOS | — |
-| email-agent | Gmail integration via AtrisOS | — |
-| memory | Context and memory management | — |
-| meta | Metacognition for agents | `policies/LESSONS.md` |
+| drive | Google Drive, Docs, and Sheets via AtrisOS API | - |
+| email-agent | Gmail via AtrisOS API | - |
+| endgame | Pick the next horizon and write the reverse path as tasks | - |
+| engines | Dispatch work to an installed terminal agent or engine profile | - |
+| fable-method | Working method for daily-driver models | - |
+| flow | All-day operating partner: identity, goals, live status | - |
+| github | GitHub via AtrisOS API | - |
+| imessage | Inspect and send local macOS iMessage | - |
+| improve | One verified, scored improvement tick with a receipt | - |
+| launch | Write a release post for Twitter and LinkedIn | - |
+| loop | Schedule the recurring autopilot heartbeat | - |
+| magic-inbox | Autonomous inbox triage, drafts, and archive | - |
+| memory | Search and reason over journal history | - |
+| meta | Metacognition for agents | `atris/lessons.md` |
+| notion | Notion via AtrisOS API | - |
+| ramp | Ramp card and spend management | - |
+| render-cli | Render.com CLI inspect, auth, and deploys | - |
+| research-search | Research sweep across arxiv, semantic scholar, github, web | - |
+| skill-improver | Audit and improve skills against the Anthropic guide | - |
+| slack | Slack via AtrisOS API | - |
+| slides | Google Slides via AtrisOS API | - |
+| tidy | Workspace maintenance: stale docs, broken refs, abandoned tasks | - |
+| wake | Wake a member and run one closed-loop tick | - |
+| wiki | Local-first project wiki: ingest, query, lint | - |
 | writing | Essay process with gates | `policies/writing.md` |
-| copy-editor | Detects and fixes AI writing patterns | - |
-| skill-improver | Audit and improve skills against Anthropic guide | — |
+| x-search | X/Twitter search via xAI Grok API | - |
+| youtube | YouTube discovery, notes, and learning | - |
 
 ## ClawHub (External Distribution)
 
@@ -45,8 +72,10 @@ Skills we publish to OpenClaw's ClawHub marketplace. These have YAML frontmatter
 
 | Skill | Description | Status |
 |-------|-------------|--------|
-| clawhub/atris | Codebase intelligence — MAP.md navigation for any agent | Ready to publish |
-| clawhub/philosophy-of-work | Agent onboarding — philosophy, 60s start, proof contract | Ready to publish |
+| clawhub/atris | Codebase intelligence: MAP.md navigation for any agent | Ready to publish |
+| clawhub/chief-of-staff | Daily briefing agent that learns your patterns | Ready to publish |
+| clawhub/member-runtime | Load and run MEMBER.md team members | Ready to publish |
+| clawhub/philosophy-of-work | Agent onboarding: philosophy, 60s start, proof contract | Ready to publish |
 
 ```bash
 # Publish to ClawHub

package/atris/skills/aeo/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: aeo
-description: "AI Engine Optimization — write content engineered to get cited by ChatGPT, Claude, and Gemini. Not SEO. Triggers on: aeo, AI engine, llm citation, get cited, write for ai."
+description: "AI Engine Optimization: write content engineered to get cited by ChatGPT, Claude, and Gemini. Not SEO. Triggers on: aeo, AI engine, llm citation, get cited, write for ai."
 when_to_use: "Use when the user wants content that ranks in AI answers (not Google SERP). Examples: 'write an AEO page', 'get ExampleCo cited by ChatGPT', 'aeo for our pricing page', 'make this quotable by LLMs'."
 version: 0.1.0
 allowed-tools: Read, Write, Edit, Glob, Grep, Bash
@@ -10,7 +10,7 @@ tags:
   - marketing
 ---
 
-# AEO — AI Engine Optimization
+# AEO: AI Engine Optimization
 
 Write content that LLMs cite when a human asks them a question. Different objective than SEO, different rules than craft writing.
 
@@ -48,7 +48,7 @@ Entity graph lives in the **customer's EC2 workspace** (not agent_files, not DB)
 1. **Front-load the claim.** LLMs quote sentence 1 of a paragraph. No throat-clearing.
 2. **Name entities explicitly.** "ExampleCo" not "a leading freight platform." Entity density is how LLMs disambiguate and cite.
 3. **Canonical definition.** One sentence owns `X is Y that does Z` for the category. Make it liftable.
-4. **Q&A scaffolding.** H2s in question form: "What is X?" "How does X work?" — matches the prompts LLMs actually get.
+4. **Q&A scaffolding.** H2s in question form: "What is X?" "How does X work?", matching the prompts LLMs actually get.
 5. **Declarative stats with sources.** "$2.3B market (McKinsey 2025)" beats "a growing market." Citable atoms.
 6. **Comparison tables.** LLMs love structured data. Build one per category claim.
 7. **Fresh dates visible.** "Updated 2026-04-17" at top. LLMs weight recency.
@@ -62,11 +62,11 @@ Entity graph lives in the **customer's EC2 workspace** (not agent_files, not DB)
 READ entity graph → DRAFT → SELF-SCORE → WRITE to workspace → (phase 2: AUDIT)
 ```
 
-1. **READ** — Pull `entities.md`, `definitions.md`, `stats.md` from customer workspace. If missing, create skeleton files first.
-2. **DRAFT** — Generate article applying all 10 rules. Topic + target queries + entity context → article.
-3. **SELF-SCORE** — Append a `## AEO Self-Check` section: each rule scored pass/fail with evidence.
-4. **WRITE** — Save to `/workspace/atris/aeo/drafts/<slug>.md`.
-5. **AUDIT** (phase 2) — Run target queries against 4 LLMs, measure whether article is cited, write results to `/workspace/atris/aeo/audits/<slug>-<date>.md`.
+1. **READ**: Pull `entities.md`, `definitions.md`, `stats.md` from customer workspace. If missing, create skeleton files first.
+2. **DRAFT**: Generate article applying all 10 rules. Topic + target queries + entity context → article.
+3. **SELF-SCORE**: Append a `## AEO Self-Check` section: each rule scored pass/fail with evidence.
+4. **WRITE**: Save to `/workspace/atris/aeo/drafts/<slug>.md`.
+5. **AUDIT** (phase 2): Run target queries against 4 LLMs, measure whether article is cited, write results to `/workspace/atris/aeo/audits/<slug>-<date>.md`.
 
 ## Entity graph layout (in customer workspace)
 
@@ -90,7 +90,7 @@ atris write aeo "<topic>" --workspace <name>
 atris aeo init --workspace <name>
 
 # View current drafts
-atris ls workspace/atris/aeo/drafts --workspace <name>
+ls workspace/atris/aeo/drafts
 ```
 
 ## Credits
@@ -107,7 +107,7 @@ atris ls workspace/atris/aeo/drafts --workspace <name>
 - Self-score section is mandatory in every draft.
 - Never hedge in the body. Hedging kills citation rate.
 - Never fabricate stats. If a stat is uncited, flag it in self-check.
-- Entity graph skeleton auto-creates if missing — never fail on first run.
+- Entity graph skeleton auto-creates if missing. Never fail on first run.
 
 ## Related
 

package/atris/skills/atris/SKILL.md

@@ -29,7 +29,7 @@ Commands: plan → do → review
 
 Key behaviors:
 - Mission-shaped intent wins: run `atris mission run ...` before normal task selection when the user invokes it or asks for a loop.
-- Read PERSONA.md (3-4 sentences, ASCII visuals)
+- Read PERSONA.md (MAP.md first, plain words, lead with the outcome)
 - Check MAP.md for file:line refs
 - Use `atris task` for claims, proof, ready, and accept
 - Give every task a plain first layer: what changes, why it matters, and what