@jjanczur/tyran 0.1.0

package/.claude-plugin/marketplace.json

@@ -0,0 +1,22 @@
+{
+  "name": "tyran",
+  "metadata": {
+    "description": "Marketplace for the Tyran task conductor plugin"
+  },
+  "owner": {
+    "name": "Jacek Janczura",
+    "url": "https://github.com/jjanczur"
+  },
+  "plugins": [
+    {
+      "name": "tyran",
+      "description": "A task conductor for Claude Code: multi-agent orchestration with an enforced evidence contract, repo-specific learning, and update-safe local evolution.",
+      "version": "0.1.0",
+      "source": "./",
+      "author": {
+        "name": "Jacek Janczura",
+        "url": "https://github.com/jjanczur"
+      }
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,22 @@
+{
+  "name": "tyran",
+  "version": "0.1.0",
+  "description": "A task conductor for Claude Code: multi-agent orchestration with an enforced evidence contract, repo-specific learning, and update-safe local evolution.",
+  "author": {
+    "name": "Jacek Janczura",
+    "url": "https://github.com/jjanczur"
+  },
+  "homepage": "https://github.com/jjanczur/tyran#readme",
+  "repository": "https://github.com/jjanczur/tyran",
+  "license": "Apache-2.0",
+  "hooks": "./hooks/hooks.json",
+  "keywords": [
+    "orchestration",
+    "multi-agent",
+    "conductor",
+    "evidence",
+    "self-improvement",
+    "workflow",
+    "quality-gates"
+  ]
+}

package/CHANGELOG.md

@@ -0,0 +1,245 @@
+# Changelog
+
+## 0.1.0 — unreleased
+
+### Six protocol skills, and the budget raised once to pay for them
+
+**The conductor was ordering work it had never defined.** Rule 3 required a
+browser pass "navigation, clickability, a clean console" and an "optimization
+pass per story"; `fidelity-gate` step 4 required computed styles dumped to
+JSON; rule 4 made a human-reviewed PR the default ending. Not one of those had
+a protocol behind it, so each meant whatever the agent doing it decided that
+afternoon. Six skills now carry them — `browser-check`, `deslop`,
+`code-review`, `root-cause`, `pr-feedback`, `skill-writing` — and each is
+wired into the caller that was already asking for it. **A protocol is admitted
+here only when something names it**, which is the rule that keeps the number
+at fourteen rather than forty.
+
+Two are worth calling out. `pr-feedback` exists because GitHub keeps pull
+request feedback in three separate resources and the inline-comments endpoint
+does not contain a review's body: measured on `cli/cli` PR #13944, which has
+one review carrying written feedback and **zero** inline comments. An agent
+reading one surface there reports "all feedback addressed" — true about what
+it read, false about what it claims. And `skill-writing` exists because the
+retrospective may commit a new skill without asking (AUTO class); that is only
+safe against a standard, and it now has one, including an activation test that
+proves the skill fires from a cold session.
+
+**The description budget moved from 4000 to 5000, once, deliberately.** Every
+description is loaded into every session whether its skill fires or not, which
+is the context tax the README's "small curated core" row is about — and
+oh-my-claudecode's issue #2943 describes a budget that was *exceeded*, not one
+that was moved. So the raise came with the mechanics that make the difference
+real: `DEFAULT_BUDGET` is exported and pinned by a test; `.github/workflows/
+ci.yml` no longer carries its own `--budget 4000` copy, because the number
+living in two places meant raising one left the other enforcing a ceiling that
+existed nowhere in the repo; and raising it stays **GATED** in the autonomy
+policy — a retrospective may propose a raise and may not perform one. Current
+total: 4340 of 5000, and a test now fails if the README's quoted figures and
+the script ever disagree.
+
+**Two more guards, both for claims that decay silently.** The inventory test
+now catches a spelled-out count ("fourteen skills and four agents") that has
+gone stale, which the digit-anchored check could not see — deliberately
+matching only the two phrasings that are claims about what ships, so the
+footnote's historical "the first eight skills" stays correct. `agents/scout.md`
+gained an output contract for mapping unfamiliar code, so recon comes back as
+a one-screen map with entry points, flow and hidden coupling instead of a
+directory listing.
+
+### The loop closes: setup, four commands, a bare `/tyran`, and a retro that fires itself
+
+**The retrospective no longer depends on anyone remembering it.** A new `Stop`
+gate refuses exactly one turn when an initiative has all its tickets merged
+and nothing recorded since the last merge. It anchors on the LAST MERGE
+rather than on "any retro ever", so one old retrospective cannot silence
+every future initiative in a repo. It short-circuits on `stop_hook_active`
+before touching the filesystem, so the worst case is one extra turn and never
+a held-open session. It fails open on everything — no journal, corrupt
+journal, unreadable initiative — because being unable to prove a retro is
+owed is not evidence that one is owed. And declining is a complete answer:
+record a `retro.entry` with `kind: skipped` and it is satisfied.
+
+**`/tyran:setup` configures a repo from what is true about it.** The
+deterministic half is `scripts/scan-repo.mjs`: package manager from
+lockfiles, validation commands from the scripts the repo actually declares,
+languages by weight, and an autonomy class inferred from merge history.
+Everything carries provenance — value, source, confidence — so "why does this
+repo think it is P2" has an answer in the file. Two refusals are deliberate:
+it **never infers `P3`**, because no arrangement of files is evidence that a
+person meant to let an agent deploy to production; and it returns an EMPTY
+validation list rather than guessing `npm test`, because a guessed command
+fails for an unrelated reason and teaches the operator that the gate is noise.
+
+**`/tyran` without the colon.** Plugin skills are namespaced, so the
+conductor is `/tyran:run`. Setup offers to install a short shim into
+`.claude/skills/tyran/` that hands straight over to it — the playbook stays
+in the plugin, so updates keep reaching it. Setup asks first, because a file
+appearing in someone's working tree unannounced is a bad way to meet a tool.
+
+**Reasoning effort is now a dial of its own**, alongside the model. Most
+adjustments want one and not the other: a mechanical sweep on a strong model
+still needs no deep reasoning, and a subtle diagnosis on the middle model
+usually does. The conductor is explicitly expected to override either for a
+single subtask — that is the intended use, not an escape — with every
+deviation recorded as a `decision` event. What it cannot do is go under a
+role floor, and when a floor corrects a request the tool says so instead of
+quietly returning something else.
+
+Also: `/tyran:status`, `/tyran:doctor`, `/tyran:retro`.
+
+The doctor caught a defect in this very change: the platform builds no match
+query for `Stop`, so the matcher first written on that entry was decorative.
+It is gone, and the registry is clean.
+
+### The conductor and its roster ship: `/tyran:run` plus four agents
+
+`agents/` is no longer empty. `scout`, `implementer`, `reviewer` and `retro`
+are real files, carrying the playbook that has been conducting this project's
+own initiatives for months — the evidence contract, the lease protocol, the
+seven-point handoff, the delta rule for numeric gates, the explicit "NO
+INDEPENDENT REVIEW" stamp when review had to be skipped, and the anti-bloat
+filter whose correct answer is often *"I changed nothing"*. Two tool grants
+are load-bearing rather than incidental: the reviewer gets no editing tools,
+so it cannot patch what it is grading, and the scout is read-only apart from
+the `Bash` reconnaissance needs. Neither is presented as airtight — `Bash` can
+write, and the agent files say so.
+
+`scripts/tiers.mjs` makes model choice a one-line decision. Model names now
+appear in exactly ONE file; skills, agents and policies are written in role
+names, so a deprecation is an edit rather than a sweep. Four tiers replace
+three, because "expensive" was never one thing: `deep` buys harder reasoning,
+`top` is for calls where being wrong is both costly and hard to notice. The
+default routes everyday work to the middle tier. **Security review and
+arbitration carry a floor** that no profile and no risk flag can push them
+below — without it, `--profile eco --risk low` would have been a one-flag
+downgrade of the two judgements everything downstream trusts. A missing alias
+throws instead of falling back to the session default, because routing that
+silently does nothing is indistinguishable from routing that works.
+
+`scripts/stop-check.mjs` gives the operator a brake that needs no session:
+`echo reason > .tyran/STOP` and the conductor halts before its next spawn or
+merge. It is the one reader in this codebase that **fails closed** — an
+unreadable STOP, a STOP that is a directory, an empty STOP all stop — because
+a brake that releases itself when damaged is not a brake. `.tyran/STOP` is
+KERNEL in the shipped policy, and the docs name the hole that leaves. The idea
+is adapted from pro-workflow's file kill-switch; the code and semantics are
+ours.
+
+The README stops under-claiming in three places and over-claiming in one: the
+principle that read *"autonomy … never self-escalated"* now says what was
+measured instead.
+
+### The enforcement epic is complete: five hooks, and a doctor that catches a dead one
+
+`policy-gate.mjs` turns the autonomy classes into a refusal: path classes
+(AUTO/GATED/KERNEL), a deployment class for `git push`, and one narrow rule on
+READS. The read rule exists because a neighbouring project's `.env` was pulled
+into a session here in full, unasked — the secrets gate defends PUBLICATION,
+and that leak arrived by a READ.
+
+`write-guard.mjs` keeps a control character out of a file on every writing
+tool, MCP servers included, and decodes shell escapes so `printf '\U000E0041'`
+stops being the way around it. `hooks-check.mjs` answers the question the
+plugin could not answer about itself: is a declared gate actually able to fire?
+It reports a missing file, a lost execute bit, a matcher that matches nothing,
+and — measured from the platform's own entry schema — the four keys that
+silently disarm a gate while everything else still looks healthy.
+
+Named honestly: the doctor DETECTS, it does not ENFORCE. It cannot refuse
+anything.
+
+### Banner replaced
+
+The hero image is now the code-forging hall: a conductor and a floor of agent
+workstations, each screen showing its own state — 65% done, a critical logic
+failure, data gathering stalled, self-improvement required. It says what the
+product is about better than the pyramid did: the state is on the wall, not in
+somebody's summary.
+
+### README: claims narrowed to what exists
+
+Three bullets described a retrospective agent, a delta-review agent and
+role-based cost routing in the present tense. None of them has any code, and
+`agents/` is empty — scout, implementer and reviewer are a design, not a file.
+They are marked as designed-not-built now. The status box lists shipped versus
+unbuilt, the roadmap ticks the two epics that are done, and the comparison
+table flips three rows from committed to shipped.
+
+One claim was not merely early but false, and the review disproved it by
+measurement: *"deployment autonomy classes are never self-escalated."* The file
+holding the class is GATED, not KERNEL, so an agent with a broad allow-list can
+raise it in the main loop. The README says that now.
+
+### The evidence contract is now a gate, not a request
+
+`hooks/scripts/evidence-gate.mjs` runs on `SubagentStop` and refuses a report
+from an implementer or a reviewer that carries no raw command output. The
+refusal names what to add and reaches the agent's context, which takes another
+turn.
+
+**It blocks SILENCE, not FORGERY** — an invented `232 passed / 0 failed` walks
+through it. See [`docs/evidence-gate.md`](docs/evidence-gate.md) for the
+criterion, the roles it binds, the recorded `EVIDENCE: none-required` escape
+hatch, and the measurements behind all three (53 of 55 real reports from this
+project's own agents pass; both misses were not reports).
+
+Every decision, including every exemption, is written to the initiative journal
+as a `gate` event, so "how often did someone opt out" is a question with an
+answer. `stop_hook_active` caps the cost at one extra turn per agent.
+
+### Behaviour change: invisible characters are SHOWN, not deleted
+
+Projections used to delete invisible codepoints (bidi overrides, zero-width
+marks, TAG characters) from journal values. They now render them as escape
+notation — `<U+202E>` — because deleting them made a poisoned value and a
+clean one look identical, and **ADR-19** requires that an exclusion never be
+silent.
+
+**Do you need to regenerate `STATE.md` / `PROGRESS.md`?** Measured, both ways:
+
+- A journal that never contained an invisible character produces
+  **byte-identical** projections before and after. `project.mjs --check`
+  stays green; nothing to do.
+- A journal that *did* contain one drifts, and `--check` exits 1. That drift
+  is the point: the projection on disk was hiding characters that were in the
+  journal. Regenerate it with the command `--check` already prints:
+  `node scripts/project.mjs <journal.jsonl> --out-dir <dir>`.
+
+The same rule now covers every operator-facing channel, not just the two
+documents: `project.mjs` warnings on stderr, every `journal.mjs` subcommand
+(as JSON `\uXXXX`, so the output still parses back identically), the
+`doctor.mjs` report, the session-start context injection, `schema.mjs` and
+`desc-budget.mjs`. `yaml-lite.stringify` refuses to serialize such a value at
+all, since this YAML subset has no escape that survives a round trip.
+
+- Plugin skeleton: manifest, single-plugin marketplace, directory layout.
+- `/tyran:hello` installation smoke-test skill.
+- CI: unit tests (`node --test`), skill description budget guard
+  (`scripts/desc-budget.mjs`), plugin manifest validation, gitleaks scan.
+- Contributor guide with the zero-dependency / no-build-step core rule.
+- Secrets gate (`hooks/scripts/secrets-gate.mjs`, `PreToolUse` / `Bash`). The
+  gate assembles the payload itself — objects from `git diff --raw` /
+  `git rev-list --objects`, contents from `git cat-file --batch`, none of
+  which consult `.gitattributes` — pipes it to `gitleaks stdin`, and refuses
+  unless the scanner reports reading exactly the bytes it was sent. It models
+  the shell's working directory across `cd`/`pushd`/`popd` and refuses any
+  movement it cannot follow rather than guessing. A push is measured against
+  the remote it targets, not against every remote. `gh release`/`gist` uploads
+  are read from disk. `--no-verify` and its abbreviations, `core.hooksPath`
+  overrides, `--force` pushes (not `--force-with-lease`) and `kill -9` (all
+  spellings, including `kill -n 9`) are refused without scanning. Suppression
+  files are honoured only when git tracks them. A refusal never carries the
+  scanner's match, elides long opaque runs in paths, and filters rule ids
+  through an allowlist. Declared limits, false-alarm rates and the scanner's
+  own measured false negatives are in `docs/hooks.md`.
+- CI installs gitleaks (pinned by version and sha256) and fails if any test
+  was skipped, so the gate's real-binary test cannot silently not run.
+
+### docs (0.1.0, pre-release)
+
+- Brand identity: hero banner (pharaoh conductor, agents building a pyramid),
+  README v2 with honest status labels and a receipts-footnoted comparison.
+- docs/: getting-started, configuration, architecture, self-improvement, FAQ.
+- Security workflow: gitleaks + semgrep (p/ci); all Actions pinned to commit
+  SHAs, semgrep container pinned to image digest.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.