Repository navigation
Agent Z Questions
Lucas (SatoshiUNO) edited this page Oct 5, 2026
·
2 revisions
Default policy: systemx-agent-z, version 1.1.0.
These are the same ordered questions used on each review under this policy. See Agent Z for evidence rules, scores, unknowns, applicability, versioned customization, and retained scorecards. Policy source.
| ID | Question |
|---|---|
| Z01.01 | Is the intended outcome stated clearly? |
| Z01.02 | Is the subject of this review identified precisely? |
| Z01.03 | Is the intended user or beneficiary identified? |
| Z01.04 | Are the original acceptance criteria available? |
| Z01.05 | Are success criteria observable rather than subjective claims? |
| Z01.06 | Are explicit non-goals recorded? |
| Z01.07 | Are important constraints recorded? |
| Z01.08 | Are assumptions separated from confirmed requirements? |
| Z01.09 | Does the result or proposed action address the original objective? |
| Z01.10 | Is any remaining acceptance gap stated clearly? |
| ID | Question |
|---|---|
| Z02.01 | Is the active workspace or project explicitly selected? |
| Z02.02 | Are permitted files and systems identified? |
| Z02.03 | Are applicable instruction and policy sources identified? |
| Z02.04 | Is the requested action within the user's authorization? |
| Z02.05 | Are consequential external actions separately authorized when required? |
| Z02.06 | Are unrelated local changes preserved? |
| Z02.07 | Is each shared resource assigned a clear owner? |
| Z02.08 | Are agent role records distinguished from running processes? |
| Z02.09 | Are cross-project actions explicitly scoped? |
| Z02.10 | Is the stopping or escalation condition clear? |
| ID | Question |
|---|---|
| Z03.01 | Are the relevant source records identified? |
| Z03.02 | Is the source revision or input version recorded? |
| Z03.03 | Are facts separated from proposals and interpretations? |
| Z03.04 | Are volatile facts checked recently enough for this decision? |
| Z03.05 | Can important claims be traced to original evidence? |
| Z03.06 | Was each decisive claim corroborated by a second independent source where feasible, with conflicts reconciled or flagged? |
| Z03.07 | Are imported documents treated as reference data within the instruction hierarchy? |
| Z03.08 | Is private context limited to the selected scope? |
| Z03.09 | Are unresolved questions retained instead of filled with guesses? |
| Z03.10 | Can another reviewer reconstruct the relevant context from the references? |
| ID | Question |
|---|---|
| Z04.01 | Is the next action concrete and bounded? |
| Z04.02 | Are task dependencies identified? |
| Z04.03 | Are prerequisites verified before dependent work proceeds? |
| Z04.04 | Is ownership clear for the work being reviewed? |
| Z04.05 | Is the plan proportionate to the problem? |
| Z04.06 | Are parallel assignments non-overlapping or explicitly coordinated? |
| Z04.07 | Are time, capacity, and tool constraints considered? |
| Z04.08 | Is recovery from an interrupted step described where needed? |
| Z04.09 | Does the plan preserve prior accepted work? |
| Z04.10 | Does further work have a stated reason rather than an automatic repeat loop? |
| ID | Question |
|---|---|
| Z05.01 | Does the deliverable satisfy the reviewed requirements? |
| Z05.02 | Are the main inputs and outputs defined? |
| Z05.03 | Are invalid or missing inputs handled explicitly? |
| Z05.04 | Are relevant boundary conditions handled? |
| Z05.05 | Are failure paths understandable and recoverable? |
| Z05.06 | Are existing supported behaviors preserved? |
| Z05.07 | Are state changes internally consistent? |
| Z05.08 | Are unnecessary dependencies or project-specific assumptions avoided? |
| Z05.09 | Are repeated operations safe for the intended workflow? |
| Z05.10 | Are known defects or incomplete parts disclosed? |
| ID | Question |
|---|---|
| Z06.01 | Are checks matched to the acceptance criteria? |
| Z06.02 | Were the relevant checks actually performed? |
| Z06.03 | Are the exact checked inputs or revisions recorded? |
| Z06.04 | Are check results and execution times recorded? |
| Z06.05 | Are failed and skipped checks visible? |
| Z06.06 | Was each decisive check shown able to fail on a known-bad, negative, or refusal input where relevant? |
| Z06.07 | Are modified components checked together where relevant? |
| Z06.08 | Is stale evidence distinguished from current verification? |
| Z06.09 | Is claimed completion supported by original evidence? |
| Z06.10 | Is the scope of each verification claim stated accurately? |
| ID | Question |
|---|---|
| Z07.01 | Are secrets excluded from source, prompts, and public artifacts? |
| Z07.02 | Are sensitive records kept within their authorized audience? |
| Z07.03 | Are path and project boundaries respected? |
| Z07.04 | Are untrusted inputs validated before use? |
| Z07.05 | Are external commands or tools invoked with explicit arguments and scope? |
| Z07.06 | Are permissions limited to what the requested action needs? |
| Z07.07 | Are dependencies and external services necessary and identified? |
| Z07.08 | Are destructive changes prevented or recoverable within the authorized workflow? |
| Z07.09 | Are logs useful without exposing unnecessary private data? |
| Z07.10 | Are material security or privacy uncertainties disclosed? |
| ID | Question |
|---|---|
| Z08.01 | Is the result understandable to its intended audience? |
| Z08.02 | Are setup steps complete for the supported environment? |
| Z08.03 | Are examples generic or clearly labeled as project-specific? |
| Z08.04 | Are names, paths, and exact casing consistent? |
| Z08.05 | Are errors actionable without hiding the failed operation? |
| Z08.06 | Are configuration and customization boundaries explained? |
| Z08.07 | Are important limitations stated alongside the relevant feature? |
| Z08.08 | Are the affected documentation and references current? |
| Z08.09 | Can a new user follow the intended workflow without guessing missing steps? |
| Z08.10 | Are accessibility or equivalent access needs addressed where relevant? |
| ID | Question |
|---|---|
| Z09.01 | Is implemented work distinguished from delivered or deployed work? |
| Z09.02 | Is the intended delivery target identified? |
| Z09.03 | Is the actual delivered revision or artifact identified? |
| Z09.04 | Is the live or installed state observed rather than inferred from source checks? |
| Z09.05 | Are configuration and environment differences accounted for? |
| Z09.06 | Are update and compatibility effects understood? |
| Z09.07 | Are rollback, backup, or removal paths appropriate to the change? |
| Z09.08 | Are post-delivery checks tied to the actual delivered revision? |
| Z09.09 | Are known differences between source and live state recorded? |
| Z09.10 | Is operational ownership clear after handoff? |
| ID | Question |
|---|---|
| Z10.01 | Are relevant timestamps timezone-aware and unambiguous? |
| Z10.02 | Are event occurrence times distinguished from recording times? |
| Z10.03 | Are due items assigned an owner and explicit state? |
| Z10.04 | Are planned schedules distinguished from executed jobs? |
| Z10.05 | Are retries or repeated events identified without duplicating effects? |
| Z10.06 | Does the handoff preserve the current objective and next action? |
| Z10.07 | Are changed code, evidence, environment, or policy inputs identified since the prior review? |
| Z10.08 | Are comparable review scores based on the same question set and policy version? |
| Z10.09 | Are unchanged results reused instead of reprocessed automatically? |
| Z10.10 | Is the remaining difference between idea, implementation, verification, and live state explicit? |
.SYSTEMX · DOT SYSTEMX · Maintained by Wayne Tech Lab LLC · Repository · User manual · Prompt cookbook · MIT license
Beta 1.11.0-beta.4 prerelease — validate the selected release in your project. Release policy. Project records, configured commands, and verified evidence determine the state of each adopted project.
DOT SYSTEMX · User manual
1. Start here
- The Guided Folder: 4K walkthrough and visual chapter index
- Start with a Folder: 4K animated guide
- Introduction video and archived poster
- Advanced walkthrough: inside the coordination layer
- Choose a workspace
- Agent 0 roster: roles, bots, and CLI paths
- Agent 0 and toolchain direct I/O
- First-time setup
- Provider and harness onboarding
- Daily workflow
- One-shot project guide
- Shared workspaces, clouds, and bots
- Historical use-case workflows
- Four current system maps
- Current maps, seven agent guides, and atlas
- Agent guide text and CLI flows
- Visual guide and historical diagrams
- New chat setup prompt
- Prompt cookbook
2. Work and continuity
- SYSTEMX PROJECTS
- AUTOBOT and Agent Alpha: Tier 2
- Local DATA storage
- Planning and memory
- ROOT planning, rules, and task delta
- System MAP
- Access Matrix: 20 standard entries
- Agent Beta, Agent1, and Agenda
- Task workflow
- Agent X: events and time
- Agent Y: CLI and PR channels
- Agent Z: fixed review
- 100 review questions
- Agent 0 and subagents
- Subagent processing
- Advanced use cases
- Evidence and acceptance
- Anti-drift and long-running work
- Tokens, cost, and time
3. Setup and maintenance
- Project / VS Code
- OS directory
- Google Drive
- LLM chat
- Exact casing and alias
- Installation and updates
- Upgrading
- Uninstall and cleanup
4. Advanced reference
- Standard format
- Technical Guide
- Stack Guide
- Library integration
- CLI and Tools
- Command reference
- Configuration and quality
- Operations and troubleshooting
- Security and support
- Code review and readiness
5. Project information