Register the AXI framework evaluation in the orchestrator boundary - #216
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the AXI (axi.md) evaluation to the surfaces-evaluated register in docs/dev/orchestrator-boundary.md, following the Next.js/GTM entry pattern.
Verdict: evaluated, not adopted. wpd meets six of the ten principles by its own route (TOON, rollups, empty states, truncation, next-step hints, per-subcommand help); session hooks, content-first no-args output, and a --fields projection are declined under the lean-surface test. The one real defect AXI surfaces — exit 1 covering a blown gate, a bad flag, and a missing file alike — is queued as a 2.0 breaking cleanup in #173 (usage errors move to exit 2).
Docs only, no behavior change, no changeset.