polyctl 0.7.0__tar.gz → 0.8.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (169) hide show
  1. {polyctl-0.7.0 → polyctl-0.8.0}/.gitignore +4 -0
  2. {polyctl-0.7.0 → polyctl-0.8.0}/PKG-INFO +10 -3
  3. {polyctl-0.7.0 → polyctl-0.8.0}/README.md +9 -2
  4. {polyctl-0.7.0 → polyctl-0.8.0}/README.tr.md +8 -2
  5. polyctl-0.8.0/docs/DOGRULAMA.md +105 -0
  6. polyctl-0.8.0/docs/GELISTIRME_LISTESI.md +92 -0
  7. {polyctl-0.7.0 → polyctl-0.8.0}/docs/adapters.md +18 -0
  8. polyctl-0.8.0/docs/archon.md +73 -0
  9. {polyctl-0.7.0 → polyctl-0.8.0}/docs/commands.md +11 -9
  10. {polyctl-0.7.0 → polyctl-0.8.0}/docs/commands.tr.md +10 -9
  11. {polyctl-0.7.0 → polyctl-0.8.0}/docs/configuration.md +20 -1
  12. {polyctl-0.7.0 → polyctl-0.8.0}/docs/features.md +4 -3
  13. {polyctl-0.7.0 → polyctl-0.8.0}/docs/getting-started.md +19 -0
  14. {polyctl-0.7.0 → polyctl-0.8.0}/docs/ledger.md +10 -0
  15. {polyctl-0.7.0 → polyctl-0.8.0}/docs/messaging.md +3 -3
  16. {polyctl-0.7.0 → polyctl-0.8.0}/docs/parallel.md +2 -2
  17. {polyctl-0.7.0 → polyctl-0.8.0}/docs/pr.md +25 -6
  18. {polyctl-0.7.0 → polyctl-0.8.0}/docs/privacy.md +2 -2
  19. {polyctl-0.7.0 → polyctl-0.8.0}/docs/release.md +4 -6
  20. {polyctl-0.7.0 → polyctl-0.8.0}/docs/safety.md +10 -0
  21. {polyctl-0.7.0 → polyctl-0.8.0}/docs/slices.md +74 -0
  22. polyctl-0.8.0/docs/slices.tr.md +85 -0
  23. polyctl-0.8.0/docs/specs.md +83 -0
  24. {polyctl-0.7.0 → polyctl-0.8.0}/docs/upstream.md +2 -0
  25. {polyctl-0.7.0 → polyctl-0.8.0}/docs/windows.md +13 -13
  26. {polyctl-0.7.0 → polyctl-0.8.0}/pyproject.toml +2 -0
  27. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/__init__.py +1 -1
  28. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/claude-code.json +7 -3
  29. polyctl-0.8.0/src/polyctl/adapters/harnessrouter.json +83 -0
  30. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/qoder.json +1 -1
  31. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/qwen.json +1 -1
  32. polyctl-0.8.0/src/polyctl/adapters/vendors.json +53 -0
  33. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/api_review.py +152 -21
  34. polyctl-0.8.0/src/polyctl/archon.py +582 -0
  35. polyctl-0.8.0/src/polyctl/billing.py +329 -0
  36. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/cli.py +148 -8
  37. polyctl-0.8.0/src/polyctl/compliance.py +372 -0
  38. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/language.py +22 -4
  39. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/lib.py +137 -5
  40. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/mcp.py +47 -17
  41. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_authority.py +54 -7
  42. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_channels.py +75 -12
  43. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_checks.py +322 -9
  44. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_harness.py +4 -0
  45. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_maintenance.py +32 -9
  46. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_pr.py +3 -2
  47. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_project.py +121 -6
  48. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_review.py +153 -7
  49. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_status.py +121 -21
  50. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/lib_adapters.py +96 -18
  51. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/lib_alarms.py +394 -2
  52. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/lib_mail.py +346 -54
  53. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/lib_next.py +11 -4
  54. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/lib_slices.py +171 -18
  55. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/lib_state.py +97 -16
  56. polyctl-0.8.0/src/polyctl/policy.py +298 -0
  57. polyctl-0.8.0/src/polyctl/security.py +208 -0
  58. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/settings.py +3 -0
  59. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/skill/SKILL.md +33 -9
  60. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/skillkit.py +5 -2
  61. polyctl-0.8.0/src/polyctl/specs.py +151 -0
  62. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/watchdog.py +79 -0
  63. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/web.py +124 -0
  64. polyctl-0.7.0/src/polyctl/adapters/vendors.json +0 -42
  65. {polyctl-0.7.0 → polyctl-0.8.0}/LICENSE +0 -0
  66. {polyctl-0.7.0 → polyctl-0.8.0}/docs/adr/0001-durable-jsonl-storage.md +0 -0
  67. {polyctl-0.7.0 → polyctl-0.8.0}/docs/adr/0002-immutable-index-candidate-authority.md +0 -0
  68. {polyctl-0.7.0 → polyctl-0.8.0}/docs/adr/0003-declarative-capability-routing.md +0 -0
  69. {polyctl-0.7.0 → polyctl-0.8.0}/docs/adr/README.md +0 -0
  70. {polyctl-0.7.0 → polyctl-0.8.0}/docs/alarms.md +0 -0
  71. {polyctl-0.7.0 → polyctl-0.8.0}/docs/audit/2026-09-08-adversarial.md +0 -0
  72. {polyctl-0.7.0 → polyctl-0.8.0}/docs/audit/2026-09-08-closure.md +0 -0
  73. {polyctl-0.7.0 → polyctl-0.8.0}/docs/audit/2026-10-15-warp-store.md +0 -0
  74. {polyctl-0.7.0 → polyctl-0.8.0}/docs/audit/2026-10-16-harness-measure.md +0 -0
  75. {polyctl-0.7.0 → polyctl-0.8.0}/docs/audit/2026-10-16-review-collect.md +0 -0
  76. {polyctl-0.7.0 → polyctl-0.8.0}/docs/audit/2026-10-18-agy-1-4-reviewer.md +0 -0
  77. {polyctl-0.7.0 → polyctl-0.8.0}/docs/backlog.md +0 -0
  78. {polyctl-0.7.0 → polyctl-0.8.0}/docs/capability-matrix.md +0 -0
  79. {polyctl-0.7.0 → polyctl-0.8.0}/docs/cloud.md +0 -0
  80. {polyctl-0.7.0 → polyctl-0.8.0}/docs/demo.md +0 -0
  81. {polyctl-0.7.0 → polyctl-0.8.0}/docs/donor.md +0 -0
  82. {polyctl-0.7.0 → polyctl-0.8.0}/docs/evidence.md +0 -0
  83. {polyctl-0.7.0 → polyctl-0.8.0}/docs/fanout.md +0 -0
  84. {polyctl-0.7.0 → polyctl-0.8.0}/docs/gates.md +0 -0
  85. {polyctl-0.7.0 → polyctl-0.8.0}/docs/github-action.md +0 -0
  86. {polyctl-0.7.0 → polyctl-0.8.0}/docs/ide-extensions.md +0 -0
  87. {polyctl-0.7.0 → polyctl-0.8.0}/docs/keyflip.md +0 -0
  88. {polyctl-0.7.0 → polyctl-0.8.0}/docs/lessons.md +0 -0
  89. {polyctl-0.7.0 → polyctl-0.8.0}/docs/mcp.md +0 -0
  90. {polyctl-0.7.0 → polyctl-0.8.0}/docs/models.md +0 -0
  91. {polyctl-0.7.0 → polyctl-0.8.0}/docs/pipeline.md +0 -0
  92. {polyctl-0.7.0 → polyctl-0.8.0}/docs/profiles.md +0 -0
  93. {polyctl-0.7.0 → polyctl-0.8.0}/docs/protocol.md +0 -0
  94. {polyctl-0.7.0 → polyctl-0.8.0}/docs/recovery.md +0 -0
  95. {polyctl-0.7.0 → polyctl-0.8.0}/docs/roles.md +0 -0
  96. {polyctl-0.7.0 → polyctl-0.8.0}/docs/slices/SECRETS-2.md +0 -0
  97. {polyctl-0.7.0 → polyctl-0.8.0}/docs/slices/TRIAGE-3-MEDIUM.md +0 -0
  98. {polyctl-0.7.0 → polyctl-0.8.0}/docs/sources.md +0 -0
  99. {polyctl-0.7.0 → polyctl-0.8.0}/docs/standin.md +0 -0
  100. {polyctl-0.7.0 → polyctl-0.8.0}/docs/surfaces.md +0 -0
  101. {polyctl-0.7.0 → polyctl-0.8.0}/docs/telegram.md +0 -0
  102. {polyctl-0.7.0 → polyctl-0.8.0}/docs/telemetry.md +0 -0
  103. {polyctl-0.7.0 → polyctl-0.8.0}/docs/threat-model.md +0 -0
  104. {polyctl-0.7.0 → polyctl-0.8.0}/docs/watchdog.md +0 -0
  105. {polyctl-0.7.0 → polyctl-0.8.0}/scripts/README.md +0 -0
  106. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/__main__.py +0 -0
  107. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/a2a.py +0 -0
  108. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/a2a_mcp.py +0 -0
  109. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/acp.py +0 -0
  110. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/README.md +0 -0
  111. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/aider.json +0 -0
  112. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/amazon-q.json +0 -0
  113. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/amp.json +0 -0
  114. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/antigravity.json +0 -0
  115. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/cloud-generic.json +0 -0
  116. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/codex.json +0 -0
  117. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/command-code.json +0 -0
  118. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/copilot.json +0 -0
  119. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/cursor-agent.json +0 -0
  120. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/deepseek.json +0 -0
  121. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/droid.json +0 -0
  122. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/gemini.json +0 -0
  123. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/grok.json +0 -0
  124. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/hermes.json +0 -0
  125. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/kilocode.json +0 -0
  126. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/kimi.json +0 -0
  127. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/kiro.json +0 -0
  128. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/ollama.json +0 -0
  129. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/omp.json +0 -0
  130. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/openai-api.json +0 -0
  131. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/opencode.json +0 -0
  132. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/pi.json +0 -0
  133. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/pr-agent.json +0 -0
  134. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/profiles.json +0 -0
  135. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/reasonix.json +0 -0
  136. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/rewriters/rtk.json +0 -0
  137. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/trae.json +0 -0
  138. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/adapters/warp.json +0 -0
  139. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/allowlist.py +0 -0
  140. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/conformance_harness.py +0 -0
  141. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/demo.py +0 -0
  142. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/drivers.py +0 -0
  143. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/email.py +0 -0
  144. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/features.py +0 -0
  145. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/journal.py +0 -0
  146. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/matrix.py +0 -0
  147. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/ntfy.py +0 -0
  148. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/outbound.py +0 -0
  149. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/__init__.py +0 -0
  150. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_completion.py +0 -0
  151. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_evidence.py +0 -0
  152. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_gain.py +0 -0
  153. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_hooks.py +0 -0
  154. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_install.py +0 -0
  155. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_lanes.py +0 -0
  156. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/cli_next.py +0 -0
  157. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/lib_events.py +0 -0
  158. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/lib_evidence.py +0 -0
  159. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/lib_gates.py +0 -0
  160. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/lib_lanes.py +0 -0
  161. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/lib_pr.py +0 -0
  162. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/parts/lib_transcript.py +0 -0
  163. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/pressure.py +0 -0
  164. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/prices.json +0 -0
  165. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/procs.py +0 -0
  166. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/storage.py +0 -0
  167. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/telegram.py +0 -0
  168. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/tiers.py +0 -0
  169. {polyctl-0.7.0 → polyctl-0.8.0}/src/polyctl/verdicts.py +0 -0
@@ -16,6 +16,10 @@ agent-mail/*.md
16
16
  .polyctl/hold
17
17
  .polyctl/sessions.json
18
18
  .polyctl/lanes/
19
+ .polyctl/ledger/mail.jsonl
20
+ .polyctl/decisions/*.json
21
+ .polyctl/decisions.lock
22
+ .polyctl/mail/
19
23
 
20
24
  # This repository is public, and its own .polyctl/ state is per-checkout development
21
25
  # state: .polyctl/config.json carries absolute home paths, a session id and reviewer
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: polyctl
3
- Version: 0.7.0
3
+ Version: 0.8.0
4
4
  Summary: Your agents commit, every change is granted first or flagged: polyctl gates the change an agent staged, has a model of another family review it, refuses any other git commit in its hook, and flags a commit made around it.
5
5
  Project-URL: Homepage, https://hakkisagdic.github.io/polyctl/
6
6
  Project-URL: Source, https://github.com/hakkisagdic/polyctl
@@ -75,11 +75,13 @@ polyctl 0.7.0 is built and supported on macOS; Linux runs the test suite in CI b
75
75
  ## Five minutes to the first reviewed commit
76
76
 
77
77
  To see it first, `polyctl demo` plays one change through polyctl on a scratch project ([demo](docs/demo.md)).
78
+ The first step is `polyctl start`, the first-run wizard. The by-hand path remains `polyctl init --profile`.
78
79
 
79
80
  ```bash
80
81
  pip install polyctl # or: uv tool install polyctl
81
82
  cd your-repository
82
- polyctl init --profile agy-codex # agy (Gemini 4 Argon) implements, Codex (gpt-6-luna) reviews; or codex-agy, claude-codex
83
+ polyctl start # asks before each step; --yes runs the steps that need no person
84
+ polyctl init --profile agy-codex # by hand: agy (Gemini 4 Argon) implements, Codex (gpt-6-luna) reviews; or codex-agy, claude-codex
83
85
  git add .polyctl-project .gitignore && git commit -m "adopt polyctl"
84
86
  polyctl hooks install # from here on, only a granted candidate commits
85
87
  ```
@@ -131,10 +133,15 @@ the pre-commit hook refuses every other commit; push is never granted
131
133
  reason, and when the queue runs dry the architect is woken to refill it.
132
134
  - **Catches up.** A review you waive is recorded, and `polyctl catchup` has a reviewer of another
133
135
  family review the landed range later.
136
+ - **Checks specs.** `polyctl spec check <slice>` checks required sections, test traces and
137
+ external claim sources before feature or enterprise review; bugfix and poc findings warn
138
+ ([spec format](docs/specs.md)).
134
139
  - **Reviews safely.** A reviewer runs with tools that only read, and polyctl measures that per
135
140
  harness: kiro-cli ran untrusted tools all the same with no person to ask, so a Kiro reviewer
136
141
  runs as a read-only agent polyctl writes for it.
137
142
 
143
+ - **Sizes the process to the work.** Slice types choose gate weight: bugfix, poc, feature (default), or enterprise; lite/full still decides enforcement ([slices](docs/slices.md)).
144
+
138
145
  Every command is in [docs/commands.md](docs/commands.md).
139
146
 
140
147
  ## Install
@@ -193,7 +200,7 @@ These are not style preferences. Each one is a failure that cost real hours.
193
200
  | **full** — every capability exercised in a production run | kiro, claude-code, antigravity |
194
201
  | **partial** — reads state, some capabilities unexercised | opencode, command-code, codex, qoder, openai-api, warp |
195
202
  | **documented** — written from published docs, not yet run | cursor-agent |
196
- | **untested** — schema present, needs a first run | gemini, aider, amp, copilot, amazon-q, deepseek, ollama, droid, grok, hermes, kilocode, kimi, omp, pi, pr-agent, qwen, reasonix, trae |
203
+ | **untested** — schema present, needs a first run | gemini, aider, amp, copilot, amazon-q, deepseek, ollama, droid, grok, harnessrouter, hermes, kilocode, kimi, omp, pi, pr-agent, qwen, reasonix, trae |
197
204
 
198
205
  Warp uses `oz`; polyctl finds it in the Warp app bundle under `/Applications` or
199
206
  `~/Applications` even when it is off PATH. `polyctl init --agent warp` uses the
@@ -30,11 +30,13 @@ polyctl 0.7.0 is built and supported on macOS; Linux runs the test suite in CI b
30
30
  ## Five minutes to the first reviewed commit
31
31
 
32
32
  To see it first, `polyctl demo` plays one change through polyctl on a scratch project ([demo](docs/demo.md)).
33
+ The first step is `polyctl start`, the first-run wizard. The by-hand path remains `polyctl init --profile`.
33
34
 
34
35
  ```bash
35
36
  pip install polyctl # or: uv tool install polyctl
36
37
  cd your-repository
37
- polyctl init --profile agy-codex # agy (Gemini 4 Argon) implements, Codex (gpt-6-luna) reviews; or codex-agy, claude-codex
38
+ polyctl start # asks before each step; --yes runs the steps that need no person
39
+ polyctl init --profile agy-codex # by hand: agy (Gemini 4 Argon) implements, Codex (gpt-6-luna) reviews; or codex-agy, claude-codex
38
40
  git add .polyctl-project .gitignore && git commit -m "adopt polyctl"
39
41
  polyctl hooks install # from here on, only a granted candidate commits
40
42
  ```
@@ -86,10 +88,15 @@ the pre-commit hook refuses every other commit; push is never granted
86
88
  reason, and when the queue runs dry the architect is woken to refill it.
87
89
  - **Catches up.** A review you waive is recorded, and `polyctl catchup` has a reviewer of another
88
90
  family review the landed range later.
91
+ - **Checks specs.** `polyctl spec check <slice>` checks required sections, test traces and
92
+ external claim sources before feature or enterprise review; bugfix and poc findings warn
93
+ ([spec format](docs/specs.md)).
89
94
  - **Reviews safely.** A reviewer runs with tools that only read, and polyctl measures that per
90
95
  harness: kiro-cli ran untrusted tools all the same with no person to ask, so a Kiro reviewer
91
96
  runs as a read-only agent polyctl writes for it.
92
97
 
98
+ - **Sizes the process to the work.** Slice types choose gate weight: bugfix, poc, feature (default), or enterprise; lite/full still decides enforcement ([slices](docs/slices.md)).
99
+
93
100
  Every command is in [docs/commands.md](docs/commands.md).
94
101
 
95
102
  ## Install
@@ -148,7 +155,7 @@ These are not style preferences. Each one is a failure that cost real hours.
148
155
  | **full** — every capability exercised in a production run | kiro, claude-code, antigravity |
149
156
  | **partial** — reads state, some capabilities unexercised | opencode, command-code, codex, qoder, openai-api, warp |
150
157
  | **documented** — written from published docs, not yet run | cursor-agent |
151
- | **untested** — schema present, needs a first run | gemini, aider, amp, copilot, amazon-q, deepseek, ollama, droid, grok, hermes, kilocode, kimi, omp, pi, pr-agent, qwen, reasonix, trae |
158
+ | **untested** — schema present, needs a first run | gemini, aider, amp, copilot, amazon-q, deepseek, ollama, droid, grok, harnessrouter, hermes, kilocode, kimi, omp, pi, pr-agent, qwen, reasonix, trae |
152
159
 
153
160
  Warp uses `oz`; polyctl finds it in the Warp app bundle under `/Applications` or
154
161
  `~/Applications` even when it is off PATH. `polyctl init --agent warp` uses the
@@ -28,15 +28,18 @@ polyctl 0.7.0 macOS üzerinde geliştirilir ve desteklenir; Linux CI'da test pak
28
28
  yalnızca okuyan araçlarla çalışır.
29
29
  - **Araçlarını bırakmazsın.** `polyctl` her ajanın kendi oturum deposunu okur ve komut satırını sürer.
30
30
  Benimsemek, işini yeni bir şeyin içinde yeniden başlatmak demek değildir.
31
+ - **Kontrolleri işin türüne uyarlar.** Dilim türleri kontrol kapsamını seçer: bugfix, poc, feature (varsayılan) veya enterprise; lite/full yaptırımı belirler ([dilimler](docs/slices.tr.md)).
31
32
 
32
33
  ## İlk gözden geçirilmiş commit'e beş dakika
33
34
 
34
35
  Önce görmek istersen `polyctl demo`, bir değişikliği geçici bir projede polyctl'den geçirir ([demo](docs/demo.md)).
36
+ İlk adım `polyctl start`, ilk kurulum sihirbazıdır. Elle yol, `polyctl init --profile` olarak kalır.
35
37
 
36
38
  ```bash
37
39
  pip install polyctl # ya da: uv tool install polyctl
38
40
  cd deponun-yolu
39
- polyctl init --profile agy-codex # agy (Gemini 4 Argon) yazar, Codex (gpt-6-luna) gözden geçirir; ya da codex-agy, claude-codex
41
+ polyctl start # her adımdan önce sorar; --yes yalnız kişi gerektirmeyen adımları koşturur
42
+ polyctl init --profile agy-codex # elle: agy (Gemini 4 Argon) yazar, Codex (gpt-6-luna) gözden geçirir; ya da codex-agy, claude-codex
40
43
  git add .polyctl-project .gitignore && git commit -m "adopt polyctl"
41
44
  polyctl hooks install # bundan sonra yalnızca yetki verilmiş aday commit edilir
42
45
  ```
@@ -88,6 +91,9 @@ pre-commit hook'u başka her commit'i reddeder; push asla yetkilendirilmez
88
91
  park edilir, kuyruk boşalınca onu doldurması için mimar uyandırılır.
89
92
  - **Telafi eder.** Atladığın bir gözden geçirme kaydedilir; `polyctl catchup` inen aralığı sonradan
90
93
  başka aileden bir gözden geçirene inceletir.
94
+ - **Şartnameyi denetler.** `polyctl spec check <slice>` zorunlu bölümleri, test bağlantılarını
95
+ ve dış sistem iddialarının kaynaklarını feature veya enterprise gözden geçirmesinden önce
96
+ denetler; bugfix ve poc bulguları uyarıdır ([şartname biçimi](docs/specs.md)).
91
97
  - **Güvenle gözden geçirir.** Gözden geçiren yalnızca okuyan araçlarla çalışır ve polyctl bunu her
92
98
  harness için ölçer: kiro-cli, soracak kişi yokken güvenilmeyen araçları yine de çalıştırdığı
93
99
  için Kiro gözden geçireni, polyctl'in onun için yazdığı salt okur bir ajan olarak koşar.
@@ -151,7 +157,7 @@ söyler.
151
157
  | **full** — her yetenek gerçek koşumda sınandı | kiro, claude-code, antigravity |
152
158
  | **partial** — durumu okur, bazı yetenekler sınanmadı | opencode, command-code, codex, qoder, openai-api, warp |
153
159
  | **documented** — yayımlanmış dokümandan yazıldı, henüz koşulmadı | cursor-agent |
154
- | **untested** — şema hazır, ilk koşumu bekliyor | gemini, aider, amp, copilot, amazon-q, deepseek, ollama, droid, grok, hermes, kilocode, kimi, omp, pi, pr-agent, qwen, reasonix, trae |
160
+ | **untested** — şema hazır, ilk koşumu bekliyor | gemini, aider, amp, copilot, amazon-q, deepseek, ollama, droid, grok, harnessrouter, hermes, kilocode, kimi, omp, pi, pr-agent, qwen, reasonix, trae |
155
161
 
156
162
  Warp, `oz` kullanır; polyctl, PATH üzerinde olmasa da programı `/Applications` veya
157
163
  `~/Applications` altındaki Warp uygulama paketinde bulur. `polyctl init --agent warp`
@@ -0,0 +1,105 @@
1
+ # `polyctl mcp serve` Uçtan Uca Doğrulama ve Kök Neden Raporu (`DOGRULAMA.md`)
2
+
3
+ **Tarih:** 15 Kasım 2026
4
+ **Kapsam:** `polyctl mcp serve` uçtan uca protokol/oturum doğrulaması (`claude` ve `agy`), CLI–MCP araç eşdeğerliği (parity), son 30 günde 14 repoda neden hiçbir oturumun MCP araçlarını çağırmadığının kök neden analizi ve uygulanan çözüm.
5
+
6
+ ---
7
+
8
+ ## 1. Uçtan Uca MCP Sunucusu Doğrulaması
9
+
10
+ ### 1.1 `stdio` JSON-RPC Protokolü ve Araç/Kaynak/İstem Keşfi (Otomatik Test: `tests/test_mcp_adoption.py`)
11
+
12
+ `polyctl -C <repo> mcp serve` sunucusunun MCP `2025-06-18` (`initialize` el sıkışması) ve durumsuz MCP `2026-07-28` (`server/discover` + `params._meta`) protokol davranışları `pytest tests/test_mcp_adoption.py` ile süreç içinde deterministik olarak doğrulanmaktadır:
13
+
14
+ | JSON-RPC Metodu | İstek Parametresi | Doğrulanan Sonuç | Durum |
15
+ |---|---|---|---|
16
+ | `initialize` | `protocolVersion: "2025-06-18"` | `protocolVersion: "2025-06-18"`, `serverInfo: {"name": "polyctl"}` | Başarılı |
17
+ | `server/discover` | `_meta: {"io.modelcontextprotocol/protocolVersion": "2026-07-28"}` | `resultType: "complete"`, `supportedVersions: ["2026-07-28", "2025-06-18"]` | Başarılı |
18
+ | `tools/list` (rolsüz / `--role architect`) | `{}` | 15 araç (`polyctl_status`, `polyctl_board`, `polyctl_next`, `polyctl_candidate`, `polyctl_notices`, `polyctl_fleet`, `polyctl_inbox`, `polyctl_ack`, `polyctl_report`, `polyctl_ask`, `polyctl_decisions`, `polyctl_propose`, `polyctl_fanout`, `polyctl_watchdog`, `polyctl_verify`) | Başarılı |
19
+ | `tools/list` (`--role implementer`) | `{}` | 13 araç (`polyctl_candidate` ve `polyctl_fleet` hariç tüm uygulayıcı araçları) | Başarılı |
20
+ | `tools/list` (`--role reviewer`) | `{}` | 3 salt-okunur araç (`polyctl_status`, `polyctl_board`, `polyctl_candidate`) | Başarılı |
21
+ | `resources/list` | `{}` | 4 kaynak (`polyctl://<proje>/board`, `roles`, `ledger`, `decisions`) | Başarılı |
22
+ | `prompts/list` | `{}` | 3 istem (`status`, `land-slice`, `stuck`; `--role implementer` için `status` ve `stuck`) | Başarılı |
23
+
24
+ ---
25
+
26
+ ### 1.2 Claude Code (`claude`) Oturumunda İstemci Davranışı (Manuel İstemci Doğrulaması)
27
+
28
+ Aşağıdaki adımlar, `claude` ikilisinin kurulu olduğu geliştirici makinesinde `.mcp.json` proje kapsamı ile `local` kapsam arasındaki onay farkını doğrular (harici `claude` ikilisi gerektirdiğinden çevrimdışı birim testlerinde değil, istemci ortamında çalıştırılır):
29
+
30
+ ```sh
31
+ polyctl -C <repo> init --agent claude-code
32
+ claude mcp get polyctl
33
+ claude mcp add -s local polyctl -- polyctl -C <repo> mcp serve --role implementer
34
+ claude mcp get polyctl
35
+ ```
36
+
37
+ 1. **Varsayılan `.mcp.json` (Proje Kapsamı):**
38
+ - `skillkit.register_mcp` (`src/polyctl/skillkit.py`), `claude-code` adaptörü için `<repo>/.mcp.json` dosyasına `{"mcpServers": {"polyctl": {"command": "<exe>", "args": ["-C", "<repo>", "mcp", "serve", "--role", "<role>"]}}}` kaydını yazar (bkz. `tests/test_mcp_adoption.py`).
39
+ - Claude Code güvenlik modeli gereği `.mcp.json` içindeki proje kapsamlı sunucuları kullanıcı etkileşimli olarak onaylayana kadar `Status: ⏸ Pending approval (run claude to approve)` durumunda tutar ve `claude -p` (headless) turlarda başlatmaz.
40
+ 2. **Etkileşimli Onay veya Yerel Kapsam (`claude mcp add -s local`):**
41
+ - Kullanıcı `claude` içinde `.mcp.json` onayını verdiğinde veya aynı rol kapsamlı komutu `local` kapsamda kaydettiğinde sunucu `Status: ✔ Connected` (`Type: stdio`) durumuna geçer.
42
+
43
+ ---
44
+
45
+ ### 1.3 Antigravity (`agy`) Oturumunda İstemci Davranışı (Manuel İstemci Doğrulaması)
46
+
47
+ Aşağıdaki adımlar, `agy` ikilisinin kurulu olduğu geliştirici makinesinde kullanıcı kapsamlı MCP kaydını ve canlı araç çağrısını doğrular:
48
+
49
+ ```sh
50
+ agy mcp add polyctl-e2e -- polyctl -C <repo> mcp serve --role implementer
51
+ agy mcp list
52
+ agy --print="Call polyctl_status, polyctl_board, and polyctl_inbox and return a compact JSON summary." --dangerously-skip-permissions --output-format=json
53
+ agy mcp remove polyctl-e2e
54
+ ```
55
+
56
+ 1. **Adaptör Bildirimi (`src/polyctl/adapters/antigravity.json`):**
57
+ - `antigravity.json` içinde `"subcommands": {"mcp": ["agy", "mcp"]}` tanımlıdır ancak proje içi `mcp.file` veya `mcp.manual` alanı bulunmaz (`tests/test_mcp_adoption.py` içinde doğrulanır). Bu nedenle `polyctl init` çalışırken `agy` için otomatik MCP kaydı yazılmaz.
58
+ 2. **Kullanıcı Kapsamında Kayıt Sonrası Bağlantı:**
59
+ - `agy mcp add` ile kullanıcı kapsamına eklendiğinde `agy` oturumu `polyctl mcp serve` sunucusuna `stdio` üzerinden bağlanır ve `polyctl_status`, `polyctl_board`, `polyctl_inbox` araçlarını tek turda çağırabilir.
60
+
61
+ ---
62
+
63
+ ### 1.4 Mail, Board, Review/Candidate ve Status Araçlarının CLI ile Eşdeğerlik (Parity) Karşılaştırması
64
+
65
+ Aşağıdaki eşdeğerlik ilişkilerinin tamamı `tests/test_mcp_adoption.py` içinde gerçek CLI komutlarıyla (`cli.main`) karşılaştırılarak doğrulanmaktadır:
66
+
67
+ | Alan | MCP Aracı | CLI Komutu | Eşdeğerlik Durumu ve Yapısal Karşılaştırma |
68
+ |---|---|---|---|
69
+ | **Durum (Status)** | `polyctl_status` (`mcp.status_payload`) | `polyctl status --json` (`cli._status_json`) | **Aynı Durum Kaynağı, Farklı Üst Zarf:** `polyctl_status`, `mcp.status_payload(cfg)` üzerinden 27–28 üst düzey alanı (`project`, `root`, `state`, `adapter`, `doing`, `enforcement`, `head`, `dirty_files`, `mailbox`, `mode`, `reviews`, `turns`, `unpushed` vb.) döner. `polyctl status --json` ise aynı durum verisini `{project, root, at, implementer, workspaces, telemetry, problems, push_guard, returned_reviews, reviews, rounds, throughput, repository, mail, board, messages}` zarfıyla döner. |
70
+ | **Pano (Board)** | `polyctl_board` (`mcp.board_payload`) | `polyctl board` ve `polyctl board ready` (`cli.cmd_board`) | **Aynı Pano Durumu (`A.board_states`, `A.board_ready`):** `polyctl_board`, `{states, counts, ready, problems, a2a}` JSON nesnesini döner; `polyctl board` aynı `A.board_states(root)` verisini metin tablosu (`_board_lines`) olarak, `polyctl board ready` ise aynı `A.board_ready(root)` dilim kimliklerini satır satır basar. |
71
+ | **Sıradaki Adım (Next)** | `polyctl_next` (`mcp.next_payload`) | `polyctl next --json` (`cli.cmd_next`) | **Aynı `next_steps.collect(cfg)` Çıktısı:** `polyctl next --json` `{project, person: [...], implementer: [...]}` dönerken `polyctl_next` aynı öğeleri `{project, counts: {person, implementer}, items: person + implementer}` olarak döner (`mcp_next["items"] == cli_next["person"] + cli_next["implementer"]`). |
72
+ | **Posta Kutusu (Mail)** | `polyctl_inbox`, `polyctl_ack`, `polyctl_report` | `polyctl mail list`, `polyctl mail ack`, `polyctl mail send` | **Aynı Dosya ve Defter Kaynağı:** Aynı `agent-mail/` dosyalarını ve `.polyctl/ledger/mail.jsonl` defterini kullanır. `polyctl_inbox` ve `polyctl_ack`, güvenliği sağlamak için yalnızca sunucunun rolüne (`--role` veya `POLYCTL_ROLE`) adreslenen mesajları listeler ve tüketir (`A.addressed_to`). |
73
+ | **Kararlar (Decisions)** | `polyctl_ask`, `polyctl_decisions` | `polyctl ask`, `polyctl decisions` | **Aynı Karar Defteri (`A.ask`, `A.decisions`):** `polyctl_ask` ile açılan karar sorusu `.polyctl/ledger/decisions.jsonl` içine yazılır ve hem `polyctl_decisions` hem de `polyctl decisions` çıktısında aynı kimlik (`D-...`) ve seçeneklerle görünür. |
74
+ | **İnceleme ve Aday (Review / Candidate)** | `polyctl_candidate`, `polyctl_verify` | `polyctl review`, `polyctl verify`, `polyctl commit-ok` | **Mimari Yetki Ayrımı:** Yetki sınırı (`Authority stays in the CLI`) gereği `polyctl review`, `polyctl person-review`, `polyctl commit-ok` ve `polyctl commit` kasıtlı olarak MCP aracına dönüştürülmemiştir. Bunun yerine `polyctl_candidate`, `polyctl review` komutunun yargıladığı sahnelenmiş adayı (`A.index_candidate(root)` -> `slice`, `title`, `boundary`, `candidate`, `context`) döner; `polyctl_verify` ise `--allow-verify` ile başlatıldığında `polyctl verify` kapılarını çalıştırır. |
75
+
76
+ ---
77
+
78
+ ## 2. MCP Araçlarının Çağrılmamasının Kök Nedenleri
79
+
80
+ `.mcp.json` içinde `polyctl mcp serve` kaydı bulunan repolarda ajanların MCP yerine CLI kullanmasının **3 kök nedeni** vardır:
81
+
82
+ 1. **Kök Neden 1 — İstemci Onay ve Kayıt Engeli (`claude` `Pending approval` ve `agy` Kayıt Eksikliği):**
83
+ - **Claude Code (`claude`):** `polyctl init`, kaydı proje içi `.mcp.json` dosyasına yazar. Claude Code, `.mcp.json` içindeki sunucuları kullanıcı etkileşimli olarak onaylayana kadar `Pending approval` durumunda tutar; etkileşimli onay verilmediğinde veya `claude -p` (headless) turlarda `polyctl mcp serve` süreci başlatılmaz. Ayrıca inceleyici (`reviewer`) ve `hunt` turları `--strict-mcp-config` bayrağıyla (`src/polyctl/adapters/claude-code.json`) çalıştığından `.mcp.json` dosyasını yüklemez.
84
+ - **Antigravity (`agy`):** `src/polyctl/adapters/antigravity.json` dosyasında `mcp` bloğu bulunmadığı için `polyctl init` çalışırken `agy` için otomatik MCP kaydı oluşturulmaz.
85
+
86
+ 2. **Kök Neden 2 — Playbook (`SKILL.md`) ve `RULE_POINTER` Yönergelerinin Önce CLI Komutlarını Öğretmesi:**
87
+ - `skillkit.RULE_POINTER` (`start every turn with polyctl status and the mailbox`) ve `src/polyctl/skill/SKILL.md` (`## 3. The loop, per slice`, `## 5. Measure before concluding`, `## 12. Commands`) uygulayıcıya durum, pano ve karar sorguları için doğrudan `polyctl status`, `polyctl board`, `polyctl next`, `polyctl decisions` kabuk komutlarını öğretmekteydi.
88
+ - MCP araçlarını doğrudan öğreten `STEERING_COORD` dosyası yalnızca `directives.coordination` tanımlayan adaptörlere (yalnızca Kiro: `.kiro/steering/polyctl-coordination.md`) yazılmakta, Claude Code ve Antigravity'ye yazılmamaktaydı.
89
+
90
+ 3. **Kök Neden 3 — Yetki Adımlarının Kabuk (`Bash`) Gerektirmesi ve Mimar İzin Kısıtı:**
91
+ - `polyctl slice start`, `polyctl verify`, `polyctl review`, `polyctl commit-ok` ve `polyctl commit` adımları tasarımsal olarak CLI'da tutulduğundan (ve `claude-code.json` içindeki `architect_tools` izin listesi yalnızca `Bash(polyctl ...)` kurallarını içerdiğinden), ajanlar kabuk üzerinden CLI komutlarını çalıştırmaya devam etmiştir.
92
+
93
+ ---
94
+
95
+ ## 3. Öneri ve Uygulanan Çözüm
96
+
97
+ Uygulayıcı ajanların MCP sunucusu bağlıyken okuma ve koordinasyon adımlarında gerçekten izin verilen MCP araçlarını kullanması ve kurulumda `.mcp.json` onay / `--no-mcp` seçeneklerinin açık olması için aşağıdaki değişiklikler uygulanmıştır:
98
+
99
+ 1. **Playbook (`src/polyctl/skill/SKILL.md`) ve `RULE_POINTER` (`src/polyctl/skillkit.py`) Güncellemesi:**
100
+ - `RULE_POINTER` içine tur başlangıcında `polyctl_status` (veya `polyctl status`) ve `polyctl_inbox` (posta kutusu) kullanımı eklendi.
101
+ - `SKILL.md` içindeki **Bölüm 3 (The loop, per slice)** ve **Bölüm 5 (Measure before concluding)** güncellenerek uygulayıcının izin verilen MCP araçlarını (`polyctl_status`, `polyctl_board`, `polyctl_next`, `polyctl_inbox`, `polyctl_ack`, `polyctl_report`, `polyctl_decisions`, `polyctl_notices`, `polyctl_watchdog`) kabuk çıktısı filtrelerinden etkilenmemek için öncelikli kullanması tanımlandı; inceleyicinin salt-okunur araçları (`polyctl_status`, `polyctl_board`, `polyctl_candidate`) **Bölüm 9**'da açıklandı.
102
+ 2. **Claude Code Onay ve `--no-mcp` Kurulum Yönergeleri (`skillkit.next_steps` & `SKILL.md` Bölüm 9):**
103
+ - `polyctl init` sonrasındaki `skillkit.next_steps` çıktısına ve `SKILL.md` Bölüm 9'a, Claude Code'da `.mcp.json` içindeki rol kapsamlı (`--role`) kaydın yüklenmesi için başlangıçta onaylanması (`claude` içinde onay veya rol kapsamlı komutun `claude mcp add -s local` ile eklenmesi), Antigravity (`agy`) için `agy mcp add` kullanımı ve CLI/dosya tabanlı kurulum isteyen repolar için mevcut `polyctl init --no-mcp` seçeneği eklendi.
104
+ 3. **Uçtan Uca Otomatik Testler (`tests/test_mcp_adoption.py`):**
105
+ - `polyctl mcp serve` JSON-RPC el sıkışması (`2025-06-18` ve `2026-07-28`), rol bazlı araç listesi (`architect`, `implementer`, `reviewer`), `skillkit.register_mcp` `.mcp.json` rol kaydı, CLI–MCP çıktı eşdeğerliği (`status` tüm ortak durum alanları, `board`, `next`, `candidate`, `inbox`, `ack`, `report`, `ask`, `decisions`) ve playbook/yönerge MCP kuralları otomatik test altına alındı.
@@ -0,0 +1,92 @@
1
+ # `polyctl` — Önceliklendirilmiş Geliştirme Listesi (Backlog & Yol Haritası)
2
+
3
+ > **Tarih:** 13 Kasım 2026
4
+ > **Kaynaklar:** `docs/RAKIP_ANALIZI.md` (Özellik Matrisi boşlukları) ve `docs/GELIR_MODELI.md` (Ticarileşme gereksinimleri)
5
+ > **Önceliklendirme Formülü:** `Skor = (Gelir Etkisi [1-5] × Kullanıcı Değeri [1-5]) ÷ Efor [1-5]`
6
+ > *(P0: Skor ≥ 6.0 | P1: Skor 3.5 – 5.9 | P2: Skor < 3.5)*
7
+
8
+ ---
9
+
10
+ ## 1. Rakip Analizi Matrisindeki Tüm `yok` ve `kısmi` Kalemlerin Eşlemesi
11
+
12
+ `docs/RAKIP_ANALIZI.md` Bölüm 3'teki özellik matrisinde `polyctl` için `yok` veya `kısmi` olarak tespit edilen **10 yetenek boşluğunun tamamı** eksiksiz olarak aşağıdaki iş kalemlerine dönüştürülmüştür:
13
+
14
+ | Matris # | Matristeki Yetenek Adı | Mevcut Durum | İş Kalemi ID | Öncelik | Gelir (1-5) | Değer (1-5) | Efor (1-5) | Skor | Durum |
15
+ | :-: | :--- | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: |
16
+ | **#16** | Ticari Lisanslama, Abonelik/Ödeme (`iyzico` + Sağlayıcı Soyutlaması) ve Faturalama | `yok` | **P0-1** | **P0** | 5 | 5 | 2 | **12.5** | `[x] Tamamlandı` |
17
+ | **#13** | Ajan Token, Çağrı ve Maliyet Muhasebesi (Kullanım Ölçümü / Metering) | `kısmi` | **P0-2** | **P0** | 5 | 5 | 2 | **12.5** | `[x] Tamamlandı` |
18
+ | **#14** | Maliyet Bütçe Limitleri (Spend Caps), Kota Kesici ve Uyarılar | `yok` | **P0-2** | **P0** | 5 | 5 | 2 | **12.5** | `[x] Tamamlandı` |
19
+ | **#7** | Pre-Commit Gizli Anahtar (Secret), PII ve Güvenlik Politikası Tarayıcısı | `yok` | **P0-3** | **P0** | 4 | 5 | 2 | **10.0** | `[x] Tamamlandı` |
20
+ | **#15** | Yerel/Web Görsel Yönetişim, Filo ve FinOps Panosu (Web UI Dashboard) | `yok` | **P0-4** | **P0** | 5 | 5 | 3 | **8.3** | `[x] Tamamlandı` |
21
+ | **#10** | Kurumsal Uyumluluk Dışa Aktarımı (SOC 2 / ISO 42001 / KVKK İmzalı Kanıt Paketi) | `yok` | **P1-1** | **P1** | 5 | 4 | 4 | **5.0** | `[x] Tamamlandı` |
22
+ | **#11** | Ekip Rol Tabanlı Yetkilendirme (RBAC) ve Politika-Kod (`policy-as-code`) Motoru | `kısmi` | **P1-2** | **P1** | 4 | 4 | 3 | **5.3** | `[x] Tamamlandı` |
23
+ | **#8** | PR / CI-CD Otomatik İnceleme Entegrasyonu (GitHub Actions / GitLab CI / SARIF) | `kısmi` | **P1-3** | **P1** | 4 | 4 | 3 | **5.3** | `[ ] Bekliyor` |
24
+ | **#17** | Dış Bildirim ve İş Akışı Kancaları (Slack / Discord / Webhook / Jira) | `yok` | **P2-1** | **P2** | 3 | 3 | 3 | **3.0** | `[ ] Bekliyor` |
25
+ | **#12** | Çoklu Depo / Organizasyonel Filo Senkronizasyonu ve Merkezi Denetim | `yok` | **P2-2** | **P2** | 4 | 3 | 4 | **3.0** | `[ ] Bekliyor` |
26
+
27
+ ---
28
+
29
+ ## 2. P0 İş Kalemleri (Uygulanan Kritik Gelir ve Güvenlik Kaldıraçları)
30
+
31
+ ### [x] P0-1: Sağlayıcı Soyutlamalı Ödeme (`iyzico` + Local), Paket/Abonelik Yönetimi ve Faturalama (`billing`)
32
+ - **Matris Kalemi:** `#16` (`yok` → `var`) · **Skor:** `12.5` · **Efor:** S–M (2) · **Bağımlılık:** Yok.
33
+ - **Kapsam:** `src/polyctl/billing.py` içinde `PaymentProvider` soyutlaması:
34
+ - `IyzicoPaymentProvider`: `iyzico` Checkout Form API'si (`/payment/iyzipos/checkoutform/initialize/auth/ecom` ve `/payment/iyzipos/checkoutform/auth/ecom/detail`) `IYZWSv2` HMAC-SHA256 imza üretimi; `IYZICO_API_KEY` ve `IYZICO_SECRET_KEY` ortam değişkenlerini okur, eksik kimlikte veya doğrulanmamış ödemede (`PENDING_CHECKOUT`) kapalı-güvenli (`ok: False`) davranır; `--payment-token` ile tekil token tekrarını (`REPLAYED`), sepet/plan bağını (`basketId`), `paymentStatus == "SUCCESS"` ve `paidPrice` tutarını doğrular.
35
+ - `LocalMockPaymentProvider`: Çevrimdışı test/simülasyon sağlayıcısı (`--provider local`, `status: "SIMULATED"`, `SIM-YYYYMMDD-XXXX.json`).
36
+ - Paket kataloğu (`community`, `pro`, `team`, `enterprise`), VKN/TCKN maskelemesi (`tax_id_masked`) ve SHA-256 sağlama toplamı (`checksum_matches`) veya `POLYCTL_BILLING_SIGNING_KEY` ile HMAC-SHA256 (`integrity_verified`) doğrulamalı fatura kaydı.
37
+ - **Kabul Kriterleri:**
38
+ 1. `polyctl billing plans --currency TRY` 4 paketi, TRY/USD fiyatlarını ve kotaları listeler.
39
+ 2. `polyctl billing subscribe --plan pro --seats 1 --currency TRY --provider iyzico` ödeme formunu başlatır (`PENDING_CHECKOUT`); `--payment-token` ile ödeme doğrulandığında (veya simülasyon için `--provider local`) abonelik ve fatura kaydını oluşturur.
40
+ 3. `polyctl billing status --json` ve `polyctl billing invoices --json` aktif aboneliği ve fatura doğrulama durumunu döndürür.
41
+
42
+ ### [x] P0-2: Ajan Kullanım Ölçümü (Usage Metering), Maliyet Muhasebesi ve FinOps Bütçe Kesici (Spend Caps)
43
+ - **Matris Kalemleri:** `#13` (`kısmi` → `var`) ve `#14` (`yok` → `var`) · **Skor:** `12.5` · **Efor:** S–M (2) · **Bağımlılık:** `P0-1`.
44
+ - **Kapsam:** Aktif fatura dönemi (`YYYY-MM`) bazında hash-zincirli ve imzalı kullanım ölçümü (`record_usage`), faturalanmamış aşım (`unbilled_overage_units`) takibi, `check_budget_gate` bütçe/kota kesicisi ve `maybe_meter_cmd` ile üst-seviye `review`, `verify`, `security-scan` komutlarının otomatik ölçümü.
45
+ - **Kabul Kriterleri:**
46
+ 1. `polyctl billing meter review --model claude-sonnet-4-5 --prompt-tokens 4000 --completion-tokens 1000` ile kullanım olayı `.polyctl/billing/usage.jsonl` dosyasına hash-zincirli ve `integrity_sha256` imzalı olarak kaydedilir.
47
+ 2. Varsayılan `--soft-cap` modunda aşım uyarı üretir (`BILLING WARNING`); `polyctl billing budget --cap-try 5000 --cap-usd 150 --hard-cap` ile katı tavan etkinleştirildiğinde ise `polyctl billing budget --check` ve kapıdaki komutlar aşım durumunda çıkış kodu `1` döndürür.
48
+ 3. Paket yenileme/yükseltmede yalnızca henüz faturalanmamış aşım (`unbilled_overage_units`) önceki paketin birim fiyatından faturaya yansıtılır.
49
+
50
+ ### [x] P0-3: Pre-Commit Gizli Anahtar (Secret), PII ve Güvenlik Politikası Tarayıcısı (`security-scan`)
51
+ - **Matris Kalemi:** `#7` (`yok` → `var`) · **Skor:** `10.0` · **Efor:** S–M (2) · **Bağımlılık:** Yok.
52
+ - **Kapsam:** `src/polyctl/security.py` ve `polyctl security-scan` komutu (`SEC-001`..`SEC-008`: Anthropic, OpenAI, AWS, GitHub PAT, PEM özel anahtar, Slack/canlı ödeme anahtarı, URL içi parola ve TCKN PII). `lib.git_binary()` ile `git diff --cached --no-ext-diff --no-textconv` üzerinden staged değişiklikleri veya `--paths` ile verilen yolları tarar; PII ve gizli dizgileri son karakterlerini göstermeden maskeler (`REDACTED`).
53
+ - **Kabul Kriterleri:**
54
+ 1. `polyctl security-scan` staged diff veya `--paths` dosyalarını tarar; temizse `0`, bulgu veya git/dosya hatası varsa kapalı-güvenli `1` koduyla çıkar.
55
+ 2. Çıktıda hiçbir gizli anahtar veya TCKN açık metin olarak yer almaz.
56
+
57
+ ### [x] P0-4: Görsel Web Yönetişim, Filo ve AI FinOps Panosu (`polyctl watch --web` `/billing` Yüzeyi)
58
+ - **Matris Kalemi:** `#15` (`yok` → `var`) · **Skor:** `8.3` · **Efor:** M (3) · **Bağımlılık:** `P0-1`, `P0-2`, `P0-3`.
59
+ - **Kapsam:** `src/polyctl/web.py` ve `src/polyctl/parts/cli_status.py` içinde `/billing` HTML görünümü ve `/api/billing` JSON uç noktası (aktif paket, kota ilerleme çubuğu, bütçe durumu, son güvenlik taraması ve fatura tablosu; sıkı CSP ve sıfır harici JS).
60
+ - **Kabul Kriterleri:**
61
+ 1. `GET /billing` semantic HTML kartlarıyla abonelik, kota, bütçe, güvenlik ve fatura tablosunu sunar.
62
+ 2. `GET /api/billing` `schema_version: 1` ile abonelik, kullanım, güvenlik ve fatura verilerini JSON olarak döndürür.
63
+
64
+ ---
65
+
66
+ ## 3. P1 ve P2 İş Kalemleri (Kurumsal Uyumluluk, RBAC ve Ekosistem)
67
+
68
+ ### [x] P1-1: Kurumsal Uyumluluk ve Denetim Kanıt Paketi Dışa Aktarımı (`compliance`)
69
+ - **Matris Kalemi:** `#10` (`yok` → `var`) · **Skor:** `5.0` · **Efor:** L (4) · **Bağımlılık:** `P0-1`, `P0-2`, `P0-3`.
70
+ - **Kapsam:** `src/polyctl/compliance.py` ve `polyctl compliance` komutu:
71
+ - SOC 2 Type II (`CC6.1`, `CC7.2`, `CC8.1`), ISO/IEC 42001 (`A.6.2`, `A.8.4`, `A.9.3`) ve KVKK Madde 12 (`KVKK-M12.1`, `KVKK-M12.2`) kontrol eşlemeleri.
72
+ - Tüm hash-zincirli defterlerin (`authority.jsonl`, `verifications.jsonl`, `reviews.jsonl`, `ledger/waivers.jsonl`, `ledger/decisions.jsonl`, `plans.jsonl`, `opt-ins.jsonl`, `slices.jsonl`, `.polyctl/billing/usage.jsonl`) zincir bütünlüğü, `security-scan` PII/sır temizliği, FinOps bütçe durumu ve Git trailer (`Polyctl-Grant`, `Polyctl-Verification`, `Polyctl-Review`) kanıtlarını toplar.
73
+ - Kanıt paketini `.polyctl/compliance/bundles` dizinine ve `.polyctl/compliance/state.json` durum dosyasına SHA-256 (`bundle_digest`) ve `POLYCTL_COMPLIANCE_SIGNING_KEY` tanımlıysa HMAC-SHA256 (`integrity_sha256`, `integrity_verified: True`) imzalı olarak yazar; makine kontrol noktası (`checkpoint_path()`) ve canlı defter özetleriyle çapraz doğrular.
74
+ - **Kabul Kriterleri:**
75
+ 1. `polyctl compliance status --framework all --json` SOC 2, ISO 42001 ve KVKK kontrollerini ve defter bütünlüğünü raporlar.
76
+ 2. `polyctl compliance export --framework all --json` imzalı kanıt paketini üretir; bozuk/onaysız defter varsa kapalı-güvenli (`1`) reddeder.
77
+ 3. `polyctl compliance verify CMP-20261113-00000000` paketin SHA-256/HMAC-SHA256 imzasını, checkpoint kaydını ve canlı defter önek özetlerini doğrular; müdahale varsa `1` koduyla çıkar.
78
+
79
+ ### [x] P1-2: Ekip Rol Tabanlı Yetkilendirme (RBAC) ve Politika-Kod (`policy-as-code`) Motoru (`policy`)
80
+ - **Matris Kalemi:** `#11` (`kısmi` → `var`) · **Skor:** `5.3` · **Efor:** M (3) · **Bağımlılık:** `P0-2`, `P0-3`.
81
+ - **Kapsam:** `src/polyctl/policy.py` ve `polyctl policy` komutu:
82
+ - 6 kurumsal rol (`owner`, `admin`, `architect`, `reviewer`, `implementer`, `auditor`) ve izin matrisi (`policy:write`, `billing:write`, `compliance:export`, `commit:grant`, `code:write`, `review:submit`, `security:scan`, `audit:read`).
83
+ - `.polyctl/policy/policy.json` içinde SHA-256 (`policy_digest`) ve `POLYCTL_POLICY_SIGNING_KEY` tanımlıysa HMAC-SHA256 (`integrity_sha256`, `integrity_verified: True`) imzalı, makine kontrol noktası (`checkpoint_path()`) ile çapraz doğrulamalı politika-kod (`policy-as-code`) motoru (`max_product_lines`, `forbidden_paths_for_implementer`, `require_security_scan`, `require_cross_family_review`, `require_budget_ok`).
84
+ - **Kabul Kriterleri:**
85
+ 1. `polyctl policy init --json` ve `polyctl policy status --json` aktif RBAC bağlarını ve politika kurallarını doğrular.
86
+ 2. `polyctl policy bind --actor dev-lead --role architect --json` aktör-rol bağını imzalı olarak kaydeder.
87
+ 3. `polyctl policy check --actor implementer --permission code:write --json` yasaklı yolları, satır limitini, güvenlik taramasını, bütçe kapısını ve çapraz model ailesi kuralını denetler; ihlalde `1` koduyla çıkar.
88
+
89
+ ### Diğeri Bekleyen Kalemler
90
+ - **[ ] P1-3 (`#8`, Skor `5.3`, Efor `3`):** CI/CD Otomatik İnceleme ve SARIF 2.1.0 / JUnit Raporlama Entegrasyonu.
91
+ - **[ ] P2-1 (`#17`, Skor `3.0`, Efor `3`):** Dış Bildirim ve İş Akışı Kancaları (Slack / Discord / Genel Webhook).
92
+ - **[ ] P2-2 (`#12`, Skor `3.0`, Efor `4`):** Çoklu Depo / Organizasyonel Filo FinOps ve Kalite Toplayıcısı.
@@ -302,6 +302,23 @@ polyctl config set review.api_providers "example https://api.example.com/v1 EXAM
302
302
  polyctl role set reviewer openai-api --model example/<model> --family <family>
303
303
  ```
304
304
 
305
+ `harnessrouter` is a second tool reviewer over `polyctl-api-review`, speaking the Universal Harness Protocol
306
+ (`--protocol uhp`, `POST <base_url>/responses`) for [HarnessRouter](https://github.com/HarnessRouter/harnessrouter)
307
+ and compatible UHP gateways. It reads `HARNESSROUTER_BASE_URL` (default `http://localhost:3000/api/harness/v1`)
308
+ and `HARNESSROUTER_API_KEY` directly — matching `keyflip`'s `harnessrouter` provider preset — or a named
309
+ provider in `review.api_providers` when `--model` starts with `<provider>/`. When `--model` names a harness
310
+ and a model (`<harness_id>/<model>`, or `<provider>/<harness_id>/<model>`), the client includes
311
+ `metadata.harness_id` in the UHP payload alongside an `Idempotency-Key` header. Because UHP executes tools
312
+ inside the remote harness container and reserves the client `tools` field on `/v1/responses`, `harnessrouter`
313
+ takes no `--tree` flag and hands the reviewer the candidate diff in the prompt alone. Any UHP response whose
314
+ `metadata.model_fallback` is true or whose `model` differs from the requested model is refused so cross-family
315
+ review independence cannot silently degrade:
316
+
317
+ ```bash
318
+ export HARNESSROUTER_API_KEY=...
319
+ polyctl role set reviewer harnessrouter --model claude-code/claude-sonnet-4-6 --family anthropic
320
+ ```
321
+
305
322
  ## A prompt past one argument reaches its command another way
306
323
 
307
324
  A review prompt carries a diff of up to 400 KB and the context it is judged against, and it went to the
@@ -680,6 +697,7 @@ the adapter says so in its `disclaimer`. **Reviewer** is whether the adapter can
680
697
  | `cloud` | `cloud-generic` | partial | ineligible | Generic cloud agent (pull-request delivered) |
681
698
  | `pr-agent` | `pr-agent` | untested | eligible | PR-Agent, a tool reviewer polyctl runs over the candidate (#86) |
682
699
  | `openai-api` | `openai-api` | partial | eligible | an OpenAI-compatible chat API, through polyctl's own client, a tool reviewer (API-REVIEWER) |
700
+ | `harnessrouter` | `harnessrouter` | untested | eligible | a UHP `/v1/responses` gateway (HarnessRouter), through polyctl's own client, a tool reviewer |
683
701
 
684
702
  Warp runs `oz`, which polyctl finds on PATH or where Warp installs it:
685
703
  `/Applications/Warp.app/Contents/Resources/bin` and
@@ -0,0 +1,73 @@
1
+ # `polyctl archon` — Archon workflow bridge
2
+
3
+ `polyctl archon` is a standard-library CLI wrapper for bash nodes in Archon workflows. It talks
4
+ to Archon only by invoking the `archon` CLI on PATH and parsing its JSON output; polyctl never
5
+ imports Archon code and never assumes private paths or hosts.
6
+
7
+ ## Contract
8
+
9
+ Every `polyctl archon` subcommand prints **one JSON line** to stdout and returns one of three
10
+ exit codes:
11
+
12
+ - `0`: completed (`{"ok": true, ...}`)
13
+ - `2`: usage error, invalid arguments, missing `archon` binary on PATH, or non-JSON `archon` output
14
+ - `3`: gate refusal (`{"ok": false, "refused": "<step>", ...}`), corrupt ledger on append, or leftover worktrees/branches
15
+
16
+ The `runs` and `leftovers` subcommands call `archon workflow status --json`, and `doctor` calls
17
+ `archon --version`. These invocations target the Archon v0.14.0 CLI shape and are exercised
18
+ against a fake `archon` binary in polyctl's test suite.
19
+
20
+ ## Subcommands
21
+
22
+ ### `polyctl archon doctor`
23
+
24
+ Checks whether `archon` is on PATH, reads its optional `--version` string, reports whether this
25
+ repository holds a valid `.polyctl/config.json` (`adopted`), and checks whether polyctl's
26
+ `pre-commit` hook is installed (`hooks_installed`). Never fails when `archon` is missing.
27
+
28
+ ### `polyctl archon runs`
29
+
30
+ Runs `archon workflow status --json` and emits normalized rows `{run, workflow, state, branch}`:
31
+
32
+ ```bash
33
+ polyctl archon runs
34
+ ```
35
+
36
+ ### `polyctl archon gate`
37
+
38
+ Runs polyctl's commit gate chain inside `--worktree <dir>` using `-C` root semantics: requires a
39
+ staged candidate, runs `polyctl verify`, verifies `--review <id>` when the profile demands a review,
40
+ grants authority via `polyctl commit-ok --verify`, and commits via `polyctl commit`. Never starts a
41
+ review actor, never waives, never pushes, and never writes to any other repository or worktree.
42
+
43
+ ```bash
44
+ polyctl archon gate --worktree <dir> -m "feat: apply change" [--review <id>] [-p <profile>]
45
+ ```
46
+
47
+ ### `polyctl archon record`
48
+
49
+ Appends one hash-chained row to `.polyctl/ledger/archon.jsonl` under `polyctl-archon-row-v1`
50
+ ([ledger](ledger.md#archon-runs)). Validates that `--sha` is 7–64 hexadecimal characters.
51
+
52
+ ```bash
53
+ polyctl archon record --run <id> --event <event> --sha <sha> --undo <text> [--item <id>] [--result <text>]
54
+ ```
55
+
56
+ ### `polyctl archon notify`
57
+
58
+ Forwards an open question through polyctl's configured channels (Telegram, ntfy, e-mail) and
59
+ records a notice when `.polyctl/` is present. Never answers a pending decision.
60
+
61
+ ```bash
62
+ polyctl archon notify --run <id> --text "Approve change?"
63
+ ```
64
+
65
+ ### `polyctl archon leftovers`
66
+
67
+ Inspects `--repo <dir>` against finished Archon runs from `archon workflow status --json` and
68
+ reports any matching linked worktrees or local branches that still exist (exit `3` if any, `0` if
69
+ none). Read-only: never deletes worktrees or branches and never signals processes.
70
+
71
+ ```bash
72
+ polyctl archon leftovers --repo <dir>
73
+ ```
@@ -11,9 +11,11 @@ Every `polyctl` command and what it does (`pctl` is the short command: the same
11
11
  | `polyctl next [--json\|--short]` | what stands in the way now, and whose hand closes it: a person's items first (a harness change nobody has read, a stand-in review request awaiting its answer, urgent mail, an open proposal), then the staged candidate's landing chain at the first stage that does not hold, each with the command that closes it; `--short` prints the menu-bar line, `---`, and the dropdown lines in the plugin format SwiftBar and xbar read. Read-only: nothing is run or recorded, and a person's command is shown, never typed ([surfaces.md](surfaces.md)) |
12
12
  | `polyctl surfaces [install\|uninstall] swiftbar --dir <dir>` | write or remove polyctl's executable `polyctl.30s.sh` menu-bar plugin in the SwiftBar or xbar plugin folder you name (`--dir` is required; polyctl never guesses a folder), refusing to overwrite or remove a file that is not polyctl's own; the plugin runs `polyctl next --short` and nothing else ([surfaces.md](surfaces.md)) |
13
13
  | `polyctl board add ID "title" --acceptance "…"` | admit one item, only with its acceptance boundary |
14
+ | `polyctl slice add ID "title" --acceptance "…" [--type bugfix\|poc\|feature\|enterprise]` · `polyctl slice edit ID --type bugfix\|poc\|feature\|enterprise` | admit or re-type a slice (the architect's or a person's, recorded against hand-edit downgrades); feature is the default, bugfix and poc run quick verification while keeping cross-family review and commit-ok (diff-only review for bugfix), and enterprise requires spec checks and two reviewer families; type sets weight, lite/full sets enforcement |
14
15
  | `polyctl slice start <id>` · `polyctl slice block "…"` · `polyctl slice abandon --why "…"` | move a slice: start a queued one or resume a blocked one, park the running one with what it waits on, drop one on the record to `rejected`; each move is a line in `.polyctl/ledger/slices.jsonl`, and dropping one is the architect's or a person's ([slices.md](slices.md#commands)) |
15
16
  | `polyctl slice status [<id>]` · `polyctl slices [--open]` | where a slice stands, since when and how it got there, its rounds and its newest review's findings; every slice on one line, a row moved or removed by hand named |
16
17
  | `polyctl verify [-p full]` | run the declared gates, record the result |
18
+ | `polyctl spec check <slice>` | check required spec sections, each acceptance criterion's named test and sources on declared external claims; feature/enterprise findings stop prospective review, bugfix/poc findings warn ([specs.md](specs.md)) |
17
19
  | `polyctl commit-ok [--verify] [--by <name>] [--ask] [--digest <sha256>]` | may this tree be committed? decided from evidence; a candidate that holds only coordination paths (which include `.polyctl/` itself, such as the gate definitions in `.polyctl/gates.json` and `.polyctl/config.json`) — and no unseen harness configuration (`polyctl harness seen --ask` first) — is granted on a person's act alone (`--by <name>` with `--ask` at an interactive terminal or `--digest <sha256>`, refused to agents) with no product gates or review (`--review`, `--verify` and `-p`/`--profile` are refused there), and recorded as a coordination commit whose trailers say so |
18
20
  | `polyctl commit -m …` · `polyctl commit-check --range A..B` | commit the granted candidate, its message ending with Polyctl- trailers that name the grant; check that each landed commit has the tree its trailers name, with no `.polyctl/` needed, as CI runs it ([gates.md](gates.md#a-commit-names-its-grant)) |
19
21
  | `polyctl hold` / `polyctl hold release --note …` | stop every agent in the tree, and keep them stopped |
@@ -24,8 +26,8 @@ Every `polyctl` command and what it does (`pctl` is the short command: the same
24
26
  | `polyctl cost --since 24h` | what the coordination itself spends: implementer turns by class (product / analysis / ceremony / coordination), wasted turns, reviews; `--since`, like every time a command takes, is `30m`, `2h`, `1d`, `today`, `yesterday` or a date; `--usd` prices the tokens in US dollars from a bundled price table, as an estimate ([telemetry.md](telemetry.md)) |
25
27
  | `polyctl export otlp [--out <file>] [--attested]` | the project's ledger as OpenTelemetry traces in the OTLP/JSON encoding (one `ExportTraceServiceRequest`): one trace per slice (its candidate) and one span per gate step (`verification`, `review`, `grant`, `commit`) with hash-derived ids and the ledger's own times, written to `--out` or stdout; refuses a ledger this machine's checkpoint store does not cover unless `--attested` asks for only the attested rows (`polyctl.export.attested_only=true`); polyctl sends nothing anywhere ([telemetry.md](telemetry.md#otlpjson-trace-export-polyctl-export-otlp)) |
26
28
  | `polyctl features [on|off <key>]` | the switches and what each costs; all off = deterministic polyctl, zero model spend ([features.md](features.md)) |
27
- | `polyctl mode [show|lite|full]` | the project mode and what each mode does and does not protect: `lite` is the basic setup without enforcement (`enforcement: off - lite` on `polyctl status`, `polyctl doctor` and the MCP status, no reviewer probe, no commit hooks, `polyctl commit` refused), a person's act with `--by <name>` on the record; `full` checks an independent reviewer route and commit hooks and refuses naming what is missing ([configuration.md](configuration.md), [safety.md](safety.md)) |
28
- | platforms | polyctl 0.7.0 is built and supported on macOS; Linux runs the test suite in CI but is not a supported platform yet; on Windows 29 tests fail (WINDOWS-LANE-0.7, docs/backlog.md) and Windows waits for a later release ([windows.md](windows.md)); the suite runs on Ubuntu for every push and pull request, on macOS weekly, and on Windows on demand until WINDOWS-LANE-0.7 |
29
+ | `polyctl mode [show|lite|full] [--by <name>] [--review-lite <choice>] [--plan]` | the project mode and what each mode does and does not protect: `lite` is the basic setup without enforcement (`enforcement: off - lite` on `polyctl status`, `polyctl doctor` and the MCP status, no reviewer probe, no commit hooks, `polyctl commit` refused), a person's act with `--by <name>` on the record that also records the `HEAD` it was set at; in `lite` mode `polyctl mode show` says how many first-parent commits are in the lite window so far; `polyctl mode full --by <name>` checks an independent reviewer route and commit hooks, refuses naming what is missing, and handles the lite window with `--review-lite all`, `--review-lite <sha>` (comma-separated window commits), or `--review-lite none` (with none of them, prints the window and how to choose and accepts all unreviewed, and `polyctl mode full --plan` prints the window and what each choice would do without writing); selected commits are reviewed against their commit messages (with another model family when known, else the project's reviewer table), findings queue one fix item per commit on the board and mail the implementer, a reviewer that cannot review leaves the commit `pending` (exit 3) for `polyctl catchup`, and unselected commits are recorded as `accepted-unreviewed` ([configuration.md](configuration.md), [safety.md](safety.md)) |
30
+ | platforms | polyctl 0.7.0 is built and supported on macOS; Linux runs the test suite in CI but is not a supported platform yet; on Windows 29 tests fail (WINDOWS-LANE-0.7, docs/backlog.md) and Windows waits for a later release ([windows.md](windows.md)); the hosted suite runs on Ubuntu for every push and pull request and nowhere else; a macOS or Windows run is started by hand |
29
31
  | `polyctl waive review\|gates [--gates <names>] --slice B7 --by <name> --why …` / `polyctl catchup` | a person bypasses `review` or `gates` on the record (`inventory` is refused, since nothing in `polyctl commit-ok` reads an inventory waiver); a `gates` waiver stands in for the failed gates it names (all of the profile's when `--gates` is omitted) on one staged candidate whose verification ran every gate of the profile; catchup re-runs waived gates on the landed commit and closes the waiver when they pass, reviews each waived review's landed range with a model family other than the one that wrote it against what its commit messages claim, closes a `move-only` split on the proof its grant recorded, run again, and replays deferred wakes and nudges. `polyctl catchup --plan` previews it, names what closes by proof, and writes nothing, `polyctl catchup --limit 10` and `polyctl catchup --slice B7` bound a run, `polyctl catchup --author-family <family> --by <name>` is a person naming a family polyctl did not record, and `polyctl catchup --move-only <slices> --by <name>` is a person stating which waived slices only moved code, each closing only where the proof holds, and `polyctl catchup --slice B7 --reviewer <actor>` reviews with another reviewer actor of the table, so runs over different slices go side by side; a run exits 3 when the reviews it started decided nothing, 1 when a waived gate failed or a ledger could not be written, and 0 when it made progress or had nothing to do |
30
32
  | `polyctl pings setup [--url-env NAME] [--all]` | dead man's switch: external pings that alarm when the watchdog and its doctor job both die; polyctl asks for the check's address and does not show it, a script names the variable that holds it, and `polyctl pings` shows where they go, never the whole address ([alarms.md](alarms.md)) |
31
33
  | `polyctl hooks [status|install|uninstall] [--allow-shared-hooks]` / `polyctl push allow` | resolve Git's effective hook path; each role is independent, and shared/external/global mutations require explicit command-wide authorization |
@@ -39,16 +41,16 @@ Every `polyctl` command and what it does (`pctl` is the short command: the same
39
41
  | `polyctl doctor --check` | quiet doctor for a scheduler: one line per problem, exit 1, alarms raised — installed as a 15-minute launchd job, or systemd user timer on Linux, by `polyctl watchdog install` |
40
42
  | `polyctl email setup` / `polyctl email test` | the red alarm channel: e-mail via formsubmit.co, no server ([alarms.md](alarms.md)) |
41
43
  | `polyctl alarms` / `polyctl alarms test --level red` | live alarm episodes and their level; test rings every channel |
42
- | `polyctl mail log` / `polyctl mail search <text>` / `polyctl mail ack <glob>` | the mail ledger: every message written and when it was consumed, searchable after deletion |
44
+ | `polyctl mail log` / `polyctl mail search <text>` / `polyctl mail ack <glob>` | the mail ledger: every message written and when it was consumed, searchable after deletion; `polyctl room search <text>` searches both pending mail in `agent-mail/` and consumed mail in the ledger/store across every registered project, naming the project and state (`pending` or `consumed`) on each hit |
43
45
  | `polyctl watchdog explain` / `polyctl watchdog trace` | why the watchdog did or did not act: measurements and verdicts of this cycle, and of the recorded ones ([watchdog.md](watchdog.md)) |
44
46
  | `polyctl source import` | admit tracker items onto the board |
45
- | `polyctl mail` · `polyctl notices` | coordination messages; alerts this project raised |
47
+ | `polyctl mail [list\|read\|send [--from <role>] [--to <role>] [--allow-empty]]` · `polyctl notices` | coordination messages (`mail send` validates and normalises `--from` and `--to` across `implementer`, `architect`, `reviewer`, `admin`, `person` and `anyone`, defaulting to `architect` → `implementer`, refuses empty bodies unless `--allow-empty`, and `mail list` shows `from → to`); alerts this project raised |
46
48
  | `polyctl watchdog install` | launchd job, or systemd user timer on Linux, that restarts a stalled agent ([watchdog.md](watchdog.md)) |
47
49
  | `polyctl mcp serve [--project all]` · `polyctl a2a serve` | expose state, read-only resources and prompts to MCP clients (`--project all` serves every registered project) / as A2A tasks |
48
50
  | `polyctl telegram setup` | alerts to your phone, decisions back from it; polyctl asks for the bot token and does not show it, finds the chats that wrote to the bot, and writes `~/.polyctl/telegram.json` itself ([telegram.md](telegram.md)) |
49
51
  | `polyctl ntfy setup --topic-url <url> [--token-env NAME]` / `polyctl ntfy test` / `polyctl ntfy status` | outbound phone alerts via ntfy.sh or your own ntfy server; writes `~/.polyctl/ntfy.json` mode 0600, reads an access token only from `$NAME` (never an argument, never printed, never logged), and sends each alert with a priority from its alarm level ([alarms.md](alarms.md)) |
50
52
  | `polyctl digest [--days N]` | what happened, read from the ledgers — also answers "why is nothing moving" |
51
- | `polyctl ask` · `polyctl answer` · `polyctl decisions` | questions answerable in one tap; free text always last; an answer must be an offered key, and `polyctl answer <D-id> <key> --change` replaces one while the first stays on the record |
53
+ | `polyctl ask [--from <role>] [--to <role>]` · `polyctl answer [--close]` · `polyctl decisions [--close <D-id>]` | questions answerable in one tap (2–8 options, with `asked_by` and `addressee`); free text always last; an answer must be an offered key, `polyctl answer <D-id> <key> --change` replaces one while the first stays on the record, and `--close` lets a person withdraw an open non-proposal question |
52
54
  | `polyctl propose "…" --why "…" [--rule-file <path>]` · `polyctl proposals` | an agent proposes a change to a rule it works under instead of editing it: recorded in the decision ledger with its evidence, and a person accepts or rejects it with `polyctl answer`; nothing writes the rule file ([protocol.md](protocol.md#changing-the-rules-an-agent-proposes-a-person-decides)) |
53
55
  | `polyctl note` | an architect message into the mailbox, through the tool |
54
56
  | `polyctl review` | review the tree with an actor that did not write it |
@@ -62,6 +64,7 @@ Every `polyctl` command and what it does (`pctl` is the short command: the same
62
64
  | `polyctl prune` | trim accumulated records and logs |
63
65
  | `polyctl doctor` · `polyctl adapters` | check the wiring; what is supported and how well |
64
66
  | `polyctl completion zsh` | print a script that completes polyctl's commands, options and choices; `bash`, `fish` and `powershell` too, installed as [getting started](getting-started.md#6-shell-completion) shows, and printed again after `polyctl update` |
67
+ | `polyctl archon doctor\|runs\|gate\|record\|notify\|leftovers` | CLI wrapper for Archon bash nodes: emit one JSON line per call (`0` ok, `2` usage or missing `archon`, `3` refused or leftovers), commit gated worktrees, record chained run events in `.polyctl/ledger/archon.jsonl`, forward questions to configured channels without answering, and list finished-run leftovers ([archon.md](archon.md)) |
65
68
  | `polyctl --version` | the installed version |
66
69
 
67
70
  Hook status separates static intent from executable enforcement. polyctl enforcement is
@@ -100,10 +103,9 @@ unless `--allow-shared-hooks` is explicit.
100
103
  ## Tests
101
104
 
102
105
  The hosted `tests` workflow runs the suite on every push to main and every pull request
103
- on Ubuntu, with Python 3.9 (the support floor) and 3.12, and on macOS every week on
104
- Python 3.12; Windows runs on demand until WINDOWS-LANE-0.7 (`gh workflow run tests -f
105
- os=windows-latest -f python=3.12`, and `-f utf8=off` without Python's UTF-8 mode, as a
106
- default install runs it; [windows.md](windows.md)). The
106
+ on Ubuntu, with Python 3.9 (the support floor) and 3.12. It has no schedule and no on-demand
107
+ lanes: a macOS or Windows run is started by hand from a branch that adds it
108
+ ([windows.md](windows.md)). The
107
109
  repository is public, so the hosted runners cost nothing, and the pre-push hook still
108
110
  runs the suite locally before a push: first the tests the pushed commits touch, then the
109
111
  whole suite, in four processes where pytest-xdist (the `dev` extra) is installed -