Skip to content

v0.4.3: gate hardening — advisory rules become enforced gates

Latest

Choose a tag to compare

@ViryaZheng ViryaZheng released this 04 Jul 04:20
530d5e2

Every previously-advisory rule is now an executable gate, a mechanical rule, or an explicit prohibition.

P0 — lock the moat: executable schema validation for the two human-in-loop gate artifacts (brief_meta / draft_meta); anti-rationalization table at 05-production's refusal gate.

P1 — no more advisory-only rules: 02-audit failure definition + meta.failed_queries[]; 03-gap executable asset gate; 06-distribution tool-level outreach prohibition; 07-reaudit verdict-frame docs + mechanical attribution ceiling.

P2 — skill-authoring best practices: content-writer trigger boundaries; CORE-EEAT benchmark vendored locally (offline scoring, zero-external-deps); progressive disclosure for content-quality-auditor; vendored-skill local-modification registry.

Full details: CHANGELOG.md