Skip to content

Dodaios is an open-source agent OS for your desktop: it runs your coding agents, browser and apps by voice or chat, on your own machine. Formerly Personal Jarvis.

docs(agents): drop the user-approval gate for game and character art references

rubenluetke10-beep57cd7b6e11f1
diff --git a/.agents/skills/game-art-pipeline/SKILL.md b/.agents/skills/game-art-pipeline/SKILL.md
index 891391c524..b71c2935f1 100644
--- a/.agents/skills/game-art-pipeline/SKILL.md
+++ b/.agents/skills/game-art-pipeline/SKILL.md
@@ -9,9 +9,9 @@ Read [the binding production standard](../../../docs/agent-society/game-art-pipe
before planning or editing world/character art. It governs workflow; existing
runtime contracts still govern integration. Run commands from the repository root.
-Start by establishing what the user authorized: pipeline setup, art direction,
-reference scene, approved-family rollout or integration. Pipeline setup does not
-authorize a redesign. Do not revive a rejected design or infer an engine change.
+Start by establishing what the user asked for: pipeline setup, art direction,
+reference scene, family rollout or integration. Do not revive a rejected design
+or infer an engine change.
Use `python scripts/art_pipeline.py init <study-id>` for a new isolated study.
Retain editable Blender sources and use the manifest-driven exporter described
@@ -24,15 +24,12 @@ building, representative character and connecting ground should demonstrate
the intended look and motion. Review appearance, readability and character separately
from collision, animation and performance checks.
-**Obtain user approval of the specific runtime reference before batch-producing
-or replacing other asset families.** Respect approval already given for that
-same scope. A passing validator or an approval record authored by an agent is
-not authorization. The evidence fingerprint prevents accidental stale approval;
-verify consent from the conversation itself.
+No separate user approval of the reference is required before batch-producing
+other asset families; verify the reference in the runtime and continue.
-After approval, derive a modular kit and roll it out by family. Keep palette,
-rig/slot, naming, material and scale conventions consistent with the approved
-reference while preserving functional differences. Preserve user imports and
+Derive a modular kit from the reference and roll it out by family. Keep palette,
+rig/slot, naming, material and scale conventions consistent with the reference
+while preserving functional differences. Preserve user imports and
saved recipes. Do not equate a large asset count with quality.
Before integration, run the existing figure/fit checks where applicable and
@@ -40,6 +37,5 @@ the actual movement/render tests for affected surfaces. Measure runtime budgets
on stated hardware. Report unavailable checks honestly. Do not write invented
evidence or silently promote review GLBs into the production catalog.
-End a handoff with the study path, current stage, approved scope, unresolved
-findings, evidence and the next action. No approval exists merely because the
-user asks a new coding agent to continue.
+End a handoff with the study path, current stage, scope, unresolved findings,
+evidence and the next action.
diff --git a/.claude/skills/game-art-pipeline/SKILL.md b/.claude/skills/game-art-pipeline/SKILL.md
index 891391c524..b71c2935f1 100644
--- a/.claude/skills/game-art-pipeline/SKILL.md
+++ b/.claude/skills/game-art-pipeline/SKILL.md
@@ -9,9 +9,9 @@ Read [the binding production standard](../../../docs/agent-society/game-art-pipe
before planning or editing world/character art. It governs workflow; existing
runtime contracts still govern integration. Run commands from the repository root.
-Start by establishing what the user authorized: pipeline setup, art direction,
-reference scene, approved-family rollout or integration. Pipeline setup does not
-authorize a redesign. Do not revive a rejected design or infer an engine change.
+Start by establishing what the user asked for: pipeline setup, art direction,
+reference scene, family rollout or integration. Do not revive a rejected design
+or infer an engine change.
Use `python scripts/art_pipeline.py init <study-id>` for a new isolated study.
Retain editable Blender sources and use the manifest-driven exporter described
@@ -24,15 +24,12 @@ building, representative character and connecting ground should demonstrate
the intended look and motion. Review appearance, readability and character separately
from collision, animation and performance checks.
-**Obtain user approval of the specific runtime reference before batch-producing
-or replacing other asset families.** Respect approval already given for that
-same scope. A passing validator or an approval record authored by an agent is
-not authorization. The evidence fingerprint prevents accidental stale approval;
-verify consent from the conversation itself.
+No separate user approval of the reference is required before batch-producing
+other asset families; verify the reference in the runtime and continue.
-After approval, derive a modular kit and roll it out by family. Keep palette,
-rig/slot, naming, material and scale conventions consistent with the approved
-reference while preserving functional differences. Preserve user imports and
+Derive a modular kit from the reference and roll it out by family. Keep palette,
+rig/slot, naming, material and scale conventions consistent with the reference
+while preserving functional differences. Preserve user imports and
saved recipes. Do not equate a large asset count with quality.
Before integration, run the existing figure/fit checks where applicable and
@@ -40,6 +37,5 @@ the actual movement/render tests for affected surfaces. Measure runtime budgets
on stated hardware. Report unavailable checks honestly. Do not write invented
evidence or silently promote review GLBs into the production catalog.
-End a handoff with the study path, current stage, approved scope, unresolved
-findings, evidence and the next action. No approval exists merely because the
-user asks a new coding agent to continue.
+End a handoff with the study path, current stage, scope, unresolved findings,
+evidence and the next action.
diff --git a/AGENTS.md b/AGENTS.md
index 837a533a33..e3ace7c484 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -170,9 +170,9 @@ history for any of them: `docs/BUGS.md`.
**World and character art:** follow `docs/agent-society/game-art-pipeline.md`
and the `game-art-pipeline` skill before creating/redesigning game assets.
-Author a small reference in Blender, verify it in the actual runtime, and obtain
-user approval of that reference before rolling its style out across asset families.
-Pipeline setup alone approves no visual redesign. Existing runtime contracts stay binding.
+Author a small reference in Blender and verify it in the actual runtime before
+rolling its style out across asset families; no separate user approval of the
+reference is required. Existing runtime contracts stay binding.
Commit each finished step (Conventional Commits). Use the coding agent's
standard Git workflow: do not artificially leave completed work local, and do
diff --git a/docs/agent-society/game-art-pipeline.md b/docs/agent-society/game-art-pipeline.md
index 7715aaec1f..0078bbb1d7 100644
--- a/docs/agent-society/game-art-pipeline.md
+++ b/docs/agent-society/game-art-pipeline.md
@@ -59,11 +59,10 @@ view angles, in motion and with the app's supported appearances. Separate
artistic findings from measured engineering results. Iterate on this small
scene until it establishes the desired visual standard.
-**Obtain the user's approval of that specific runtime reference scene before
-batch-producing or replacing further asset families.** A request to set up this
-pipeline, a technical pass, a Blender render or an agent-written approval file
-does not constitute that approval. Existing explicit approval applies within
-its stated scope; do not ask again unless the approved direction changes.
+No separate user approval of the reference scene is required before
+batch-producing or replacing further asset families (maintainer decision,
+2026-09-30). The optional approval record below stays available for studies
+that want one.
### 4. Reusable kit and family rollout