atris 3.24.0 → 3.25.1

package/atris/policies/outbound-artifact-gate.md

@@ -0,0 +1,48 @@
+# Outbound Artifact Gate
+
+Human-facing sends must ship the artifact in the format the recipient is meant to see.
+
+This applies to email, Slack, docs, decks, HTML summaries, UI screenshots, customer updates, and team updates.
+
+## Rule
+
+Never send raw artifact source to a human unless the human explicitly asked for source.
+
+Examples of raw source:
+- HTML tags in a plain-text email body.
+- Markdown code fences that are supposed to render into a page, doc, email, diagram, or UI.
+- A screenshot, deck, PDF, or UI claim without visual proof.
+- Generic copy that sounds like a template instead of this workspace and this recipient.
+
+## Required Gate
+
+Before sending, record:
+
+1. Recipient and channel.
+2. Intended format: plain text, rendered HTML, PDF, deck, screenshot, doc, or source.
+3. Render proof for HTML or visual artifacts: preview, screenshot, PDF export, rendered email receipt, or browser check.
+4. Anti-slop pass: concrete copy, no hype terms, no corporate filler, no AI-tell phrases.
+5. Approval packet: exact recipient, subject or title, final body, and attachments.
+6. Receipt after send: message id, link, file path, or explicit `not sent`.
+
+## Hard Fails
+
+Stop before send when any of these are true:
+
+- Plain text contains `<html`, `<body`, `<div`, `<table`, or other HTML tags.
+- A body contains fenced rendered source like `html`, `tsx`, `svg`, or `mermaid` that the recipient was meant to see rendered.
+- HTML email has no render proof.
+- Visual work has no visual inspection proof.
+- Copy contains anti-slop kill-list terms such as `seamlessly`, `leverage`, `robust`, `game-changing`, or `at the end of the day`.
+- The agent cannot show the exact final recipient, subject, body, and attachments before send.
+
+## Validator
+
+Run the cheap local gate before any human-facing send:
+
+```bash
+node scripts/outbound-artifact-gate.js --channel email --format plain --body-file /path/to/body.txt
+node scripts/outbound-artifact-gate.js --channel email --format html --body-file /path/to/body.html --proof-file /path/to/render-proof.txt
+```
+
+The Gmail backend MIME fix is a transport safety net. Agents still need this gate before asking approval or sending.

package/atris/skills/atris-feedback/SKILL.md

@@ -52,9 +52,8 @@ Only use this path if the CLI is unavailable (stale install, broken login).
 
 ### Setup
 
-```bash
-cd ~/arena/atrisos-backend && source venv/bin/activate
-```
+Use this only from a trusted service workspace with AWS credentials already
+configured. Do not ask end users to clone or run backend services locally.
 
 ```python
 from dotenv import load_dotenv; load_dotenv('backend/.env')

package/atris/wiki/sources/atris-labs-2026-05-10.txt

@@ -2,16 +2,13 @@ Source receipt for atris/wiki/systems/atris-labs.md
 Compiled: 2026-05-10
 
 Local evidence checked:
-- /Users/keshavrao/arena/empire/atris-customers/atris-labs/CLAUDE.md
-- /Users/keshavrao/arena/empire/atris-customers/atris-labs/context/STATUS.md
-- /Users/keshavrao/arena/empire/atris-customers/atris-labs/context/PIPELINE.md
-- /Users/keshavrao/arena/empire/atris-customers/atris-labs/team/keshav/MEMBER.md
-- /Users/keshavrao/arena/empire/atris-customers/atris-labs/team/justin/MEMBER.md
-- /Users/keshavrao/arena/empire/atris-business/atris-labs-1/apps/
-- /Users/keshavrao/arena/empire/atrisos-backend/backend/static/workspaces/atris-labs/instructions.md
-- /Users/keshavrao/arena/empire/atrisos-backend/backend/atris-labs-1/.atris/business.json
+- historical Atris Labs customer workspace docs
+- historical Atris Labs context status and pipeline notes
+- historical Atris Labs member profile notes
+- historical Atris Labs app workspace inventory
+- historical Atris Labs cloud workspace binding metadata
 
 Notes:
-- The previous wiki source /Users/keshavrao/arena/atris-business/atris-labs-1/atris/MEMBER.md is missing in this workspace.
+- The previous wiki source is missing in this workspace.
 - Available status/pipeline files are historical March 2026 artifacts.
 - Treat this page as orientation, not a live company operating report.

package/atris/wiki/sources/atris-labs-goals-2026-05-10.txt

@@ -4,12 +4,11 @@ Compiled: 2026-05-10
 Local evidence checked:
 - atris/wiki/concepts/atris-labs-goals.md before refresh
 - atris/wiki/log.md historical ingest notes for missing goals.md
-- /Users/keshavrao/arena/empire/atris-customers/atris-labs/context/STATUS.md
-- /Users/keshavrao/arena/empire/atris-customers/atris-labs/context/PIPELINE.md
-- /Users/keshavrao/arena/empire/atris-customers/atris-labs/fundraise/metrics.md
-- /Users/keshavrao/arena/empire/atris-customers/atris-labs/fundraise/story.md
+- historical Atris Labs context status and pipeline notes
+- historical Atris Labs fundraising metrics notes
+- historical Atris Labs fundraising story notes
 
 Notes:
-- The previous source /Users/keshavrao/arena/atris-business/atris-labs/goals.md is missing in this workspace.
+- The previous goals source is missing in this workspace.
 - The page is retained as historical direction only.
 - Revenue/customer counts require live verification before operational use.

package/atris.md

@@ -10,9 +10,9 @@ leave a trail another agent or human can trust.
 On session start, before responding:
 
 1. Read:
-   - `atris/logs/YYYY/YYYY-MM-DD.md`: today's journal
-   - `atris/MAP.md`: navigation
-   - `atris/wiki/STATUS.md` if present: current memory snapshot
+   - `atris/logs/YYYY/YYYY-MM-DD.md` — today's journal
+   - `atris/MAP.md` — navigation
+   - `atris/wiki/STATUS.md` if present — current memory snapshot
 
 2. Show this box, then ask what to work on if no task was already given.
 
@@ -50,36 +50,13 @@ Then:
 - do not call something complete without verification
 - do not take irreversible actions without approval from the human
 - do not hide state outside markdown, logs, diffs, or the journal
-- do not edit the rules that judge you: the reward config, the authority policy, or this file
+- do not edit the rules that judge you — the reward config, the authority policy, or this file
 
 If you cannot honor these rules, stop, write why in the journal, and ask the human before continuing.
 
 Labels used below:
-- `guarded`: checked by code or a pre-commit hook; bypassing is a bug
-- `expected`: convention; honor it or stop
-
-## taste
-
-What you ship should not read as generated. The test: if someone said "an AI made this," would they believe it instantly? If yes, that is the bug. The model has no words for restraint and it falls into gravity wells. Beat both.
-
-- **Gate it.** `atris slop detect <path>` is deterministic: no model, exit 1 on a tell, built for CI and the review stage. A finding is a fact (file:line + rule), not an opinion. `--diff`/`--staged` scopes it to changed lines for a commit gate; `--fix` repairs the safe tells. `guarded` once wired into review.
-- **Name the move.** Vague prompts make vague output. Direct with craft words: vertical rhythm, negative space, hierarchy, contrast, bolder here / quieter there, restraint. Precise language is the lever. Own it.
-- **Refuse the wells** (named so you can): purple/indigo gradients, gradient-filled text, glassmorphism, Inter/Roboto defaults, claude-beige, neon-on-dark, hero-metric rows, identical card grids, eyebrow/tracked-caps labels, pulsing live-dots, em dashes.
-- **Commit to constraints.** One distinctive font, one accent hue, a small spacing scale. Taste is subtraction, not addition.
-- **Generate it right.** `atris deck` (slides), `atris deck from <doc.md> --html` (a web page from a plain doc, in the web app's design tokens), `atris site <dir>` (a whole markdown folder into a navigable site), and `atris recap --html` (a memory-updates page) all apply the system by default: own backgrounds and fonts, never the tool's stock template. Output as an AppBlock with `--block` to drop into a web app.
-- **Compound it.** A new tell becomes a project rule in `.atris/slop.rules.json` (`atris slop rules --add`), and a project's brand lives in `.atris/theme.json` (`atris theme create` builds your own by feel, or `atris theme init` scaffolds one) so every deck, page, and site is on-brand by default, and one line of text becomes an on-brand image with `atris card` or a short video with `atris reel`. The gate and the look grow per project instead of leaning on memory. Taste lives in code, not vibes.
-
-## voice
-
-The same discipline for words. Output stays sharp no matter how bloated the context. A full context is not license to ramble.
-
-- **Lead with the move.** Answer first, support after. No preamble, no agreement reflex ("great question", "you're absolutely right").
-- **Specific over buzzy.** Name the exact thing. If you can't, you don't understand it yet; go look, don't hedge.
-- **Cut filler.** Drop "it's worth noting", "in order to", "leverage", "seamless", "robust", "delve", stacked hedges, and em dashes. `atris slop` flags the prose tells (em-dash, hype-copy) too.
-- **Bound verbosity by information, not context.** Say the load-bearing thing and stop. Length tracks what the reader needs to act, nothing more.
-- **Match the register.** The operator wants the next move; a spec wants the contract; a journal wants one line. Jargon is a lever only when shared: use the reader's precise terms, define a new one once.
-
-`expected`: this is how an Atris agent writes and builds. Shipping slop or rambling is a failure smell, same as drift or a stale task.
+- `guarded` — checked by code or a pre-commit hook; bypassing is a bug
+- `expected` — convention; honor it or stop
 
 ## task source of truth
 
@@ -144,10 +121,10 @@ The human is the constructor. You multiply. Handoff fidelity lives in the files,
 
 Move one task at a time through plan → do → review.
 
-- **plan**: read relevant files, produce an ASCII visualization, wait for approval. No code.
-- **plan-review**: the validator reads the plan fresh and signs off with `SIGNOFF:` or halts with `REJECT:` + `FIX:` + an optional `PROPOSED:` block (concrete draft of Files / Exit / Verify / Rollback to replace). Plan does not move to do without signoff. The validator is a drafting partner, not just a critic: on REJECT it proposes the sharper rubric rather than leaving the human to guess. Codex is optional escalation when `ATRIS_USE_CODEX=1` or the task carries `[codex]`.
-- **do**: claim the task with `atris task claim <id> --as <agent>`, execute step by step, add notes as reality changes, update `MAP.md` and the journal when needed.
-- **review**: run the task's verification, read the diff, run the relevant tests, finish with `atris task finish <id> --proof "..."`, and add the lesson/next task with `atris task review`.
+- **plan** — read relevant files, produce an ASCII visualization, wait for approval. No code.
+- **plan-review** — the validator reads the plan fresh and signs off with `SIGNOFF:` or halts with `REJECT:` + `FIX:` + an optional `PROPOSED:` block (concrete draft of Files / Exit / Verify / Rollback to replace). Plan does not move to do without signoff. The validator is a drafting partner, not just a critic — on REJECT it proposes the sharper rubric rather than leaving the human to guess. Codex is optional escalation when `ATRIS_USE_CODEX=1` or the task carries `[codex]`.
+- **do** — claim the task with `atris task claim <id> --as <agent>`, execute step by step, add notes as reality changes, update `MAP.md` and the journal when needed.
+- **review** — run the task's verification, read the diff, run the relevant tests, finish with `atris task finish <id> --proof "..."`, and add the lesson/next task with `atris task review`.
 
 Every stage runs the Confidence Gate before it advances:
 
@@ -200,7 +177,7 @@ Periodically, and before closing an endgame, clean:
 - **I1:** Description
 
 ## Notes
-[timestamped lines: one per discovery, decision, or tick]
+[timestamped lines — one per discovery, decision, or tick]
 ```
 
 Context is a cache. Disk is truth. Route discoveries as they happen:
@@ -218,13 +195,12 @@ Do not batch. Nothing important should live only in memory.
 
 ## failure smells
 
-If you notice these, stop and flag, do not continue:
-- **loop**: the same suggestion fires tick after tick, nothing changes on disk
-- **drift**: `MAP.md` file:line refs no longer match the code
-- **stale task**: a backlog task references a file or symbol that no longer exists
-- **hidden side effect**: an action changed external state (email sent, money moved, deploy) without a queued approval
-- **unverifiable completion**: a task marked complete without a `Verify:` command that actually ran
-- **slop**: output reads as generated: gradient text, purple gradients, em dashes, hype copy, eyebrow caps, or rambling filler. `atris slop detect` names it; fix it before shipping (see `## taste` and `## voice`)
+If you notice these, stop and flag — do not continue:
+- **loop** — the same suggestion fires tick after tick, nothing changes on disk
+- **drift** — `MAP.md` file:line refs no longer match the code
+- **stale task** — a backlog task references a file or symbol that no longer exists
+- **hidden side effect** — an action changed external state (email sent, money moved, deploy) without a queued approval
+- **unverifiable completion** — a task marked complete without a `Verify:` command that actually ran
 
 Each has real examples in `lessons.md`. Before nontrivial execution, read the relevant recent lessons.
 
@@ -241,10 +217,10 @@ Pages that summarize or reference other files declare their sources in YAML fron
 
 If any source was modified after `last_compiled`, the page is stale. Re-read the sources, update the page, bump `last_compiled`.
 
-Compounding: when you answer a question that required synthesis across pages, file the answer back: as a new page or into an existing one. Explorations accumulate.
+Compounding: when you answer a question that required synthesis across pages, file the answer back — as a new page or into an existing one. Explorations accumulate.
 
 Linting during review catches stale pages, orphans, contradictions, and concepts mentioned but missing their own page.
 
 ---
 
-*Canonical copy: workspace root `atris.md`. Project copies are distributed; `atris update` syncs them.*
+*Canonical copy: workspace root `atris.md`. Project copies are distributed; `atris update` syncs them. Full spec: `atrisDev.md`.*