Skip to content

Mythify v7.0.0

Latest

Choose a tag to compare

@github-actions github-actions released this 09 Nov 15:10
f810234

Mythify 7.0.0 narrows the tool to its job: evidence for agent work. Product
planning is removed, which is the breaking change behind the major version.
route can also show what your own routing policy file says about a task,
and the README is now a short product page with the full feature guide in
docs/guide.md. Existing .mythify/ state keeps working; leftover product
data is ignored and never deleted.

Added

  • route shows what the user's own routing policy file says about the task. With
    MYTHIFY_AGENT_POLICY (a path) or ~/.agents/policy.json present, the text
    output ends with a Delegation section and --json gains a delegation
    object: the matched policy step and action, the role with its options and
    effort (the role's tricky effort on high risk, the tier's reviewer effort for
    the reviewer role), and the review tier for the task's risk with every extra
    tier key printed as written. It is advisory: options named in the file's
    banned-model list are withheld, an effort above its ceiling or in its
    never-list is lowered to the highest allowed level (or withheld when none
    is), banned names and forbidden effort words in any printed policy text are
    replaced with [withheld] (a name containing one is partly withheld), and
    Mythify still never picks, ranks, or switches a model. Without a file the
    output is byte-for-byte unchanged; an unreadable or invalid file prints one
    [WARN] line and is ignored. Step 1 (production, deploys, servers, or money)
    prefers recall: a clause whose operative verb is an operation verb (deploy,
    ship, release, publish, promote, restart, roll back, stop or start a service),
    ssh, scp, or rsync as the main verb, a migration against production, or an explicit
    money phrase is step 1, with or without an environment word. Only clear code
    work stays build: a coding verb whose object is a code noun that the operation
    word modifies (a deploy script, an ssh client); an ambiguous prompt goes to
    step 1. The delegation review tier is at least high for step 1, and also when
    the wording names a risky-code term from the new high_tier_terms list (auth,
    billing, checkout, race, migration, secrets, and similar, whole words only),
    with the reason in the basis; route's own classification is unchanged.
    ssh, scp, and rsync are operation verbs whatever follows them, stop, start,
    restart, reload, or kill plus a service, server, container, or worker is step
    1, run or apply a migration with an environment word is step 1, "and" before
    an operation verb starts a new clause, and documentation words (docs, typo,
    notes) cancel step 1 only together with a coding verb. The image step also takes icons
    and favicons. The task-to-step terms for production, image,
    bulk, and browser_check live in a new policy_steps section of
    protocol/classification-rules.json (schema 6) and do not change the
    classification block. The protocol gains one sentence in "Delegation is your
    choice": follow the user's or project's rules on who does what, which route
    shows when a policy file is present.

Changed

  • route sends requests to write a product roadmap, PRD, RFC, specification,
    requirements document, or design document to planning (plan); without the
    product task type they had classified as trivial. These terms count only
    near a creation verb (write, draft, create, prepare, author, produce,
    outline, plan), so "What is an RFC?" still routes as a question and "inspect
    the product requirements document" as a review.
  • The README is a short product page: the problem, how it works, who it is
    for, and a quickstart that ends at a first verified step. The full feature
    tour moved to the new docs/guide.md.
  • Maintainer files moved off the top level: MAINTAINING.md,
    RELEASE-CHECKLIST.md, and ROADMAP.md now live in docs/maintainers/.
    User-facing docs no longer carry version numbers or release-history notes;
    the CHANGELOG and the architecture decision log keep that history.

Removed

  • Breaking: product planning is removed.
    mythify product ... (create, outcome, non-goal, bet, risk,
    check, approve, decide, promote, measure, show, list) is an
    unknown command and exits 64, like any other removed command. Also removed:
    the eleven product_* MCP typed tools (the mythify tool no longer lists
    product either), the product route and the prompt product packet
    (route no longer returns product, and prompts about roadmaps, priorities,
    or product strategy now route by the remaining rules, typically map or
    plan), the product task type and its classification terms, the
    product lineage kind (--parent product:NAME and lineage attach product
    are refused), the product lines in status, summary, and report
    (summary --json loses its products key and status --json its
    active_product key), plan show's product line, the "Product planning"
    section and product lines in the protocol (AGENTS.md follows), the product
    parts of the skills and docs, and docs/product-planning.md. Why: Mythify's
    job is evidence for agent work; product strategy belongs in your own tools.
    Leftover state is ignored and left in place: a .mythify/products/ folder,
    an active_product pointer, and a plan's product_ref are never read,
    written, or deleted, and ledger records with a product key stay scoped
    records that never count for a step. ROADMAP.md, which product show --markdown rendered, is now a static file of outcomes, non-goals, and bets
    at docs/maintainers/ROADMAP.md.
    An agent following the old protocol text that runs product create now gets a
    usage error and should use map create for open decisions or plan create
    for work.
  • docs/DRIFT.md and docs/evidence/ (efficacy reproduction notes and smoke
    results), which described past releases rather than the current tool.

Full changelog: v6.2.0...v7.0.0