Capabilities Reference

The Decision Matrix Engine exhaustively evaluates the full option space for any given query — including the options that are obviously wrong. This is intentional. Knowing why the bad ideas fail is considered half the work. No option is abandoned without a documented reason.

You know the rules, and so does WRAAS: every path is evaluated, every rejection is explained.

Evaluation Flow

Configuration

Parameter	Type	Default	Description
decision.include_wrong_options	boolean	true	Evaluate obviously wrong options. Setting this to false is itself an obviously wrong option and will be documented accordingly.
decision.rejection_verbosity	enum	FULL	Detail level for rejection rationale. Options: BRIEF, STANDARD, FULL, EXCESSIVE.
decision.latency_target_ms	integer	113	Target response latency in milliseconds. This value is non-negotiable.

Validates pull requests against the Conventional Commits specification and produces review feedback using Conventional Comments. A bare update commit message will not pass. It has never passed. It will not pass today. Operates at the throughput of a serial reviewer — multiple PRs per session, each evaluated to completion. The queue does not grow.

Commit Validation Flow

Example Output

$ wraas review --pr 2847 --repo platform-core

> Fetching diff... 1,204 lines changed across 23 files
> Parsing 14 commits against Conventional Commits spec...

> [FAIL] commit 3f9a1b2 — "update"
  question(blocking): what type is this? what scope? what changed?
> [FAIL] commit 7c2e4d1 — "wip"
  question(blocking): is this intentional? should this be in a branch?
> [WARN] commit 9a1f3b4 — "fix: corrected the thing"
  suggestion(non-blocking): scope omission noted. a follow-up comment has been queued.
> [PASS] commit 1d8e2f5 — "fix(auth): handle token expiry on refresh"
> [PASS] commit 4b7c9e3 — "feat(api)!: deprecate v1 endpoints"

> Review complete. 2 blocking, 1 non-blocking, 2 approved.
> 👀 (no further explanation provided) | Latency: 113ms

WRAAS operates under a strict zero-abandonment SLA. Once a request is accepted, it will not be given up on. It will not be let down. It will not run around on a deadline. Desertion rate: 0.00%. This is non-negotiable.

SLA Parameters

Metric	Target	Actual	Notes
Request abandonment rate	0.00%	0.00%	Non-negotiable. See above.
Response latency (p99)	113ms	113ms	This number is load-bearing.
Timeout behaviour	N/A	N/A	Timeouts are not a concept WRAAS has accepted.
PTO availability	0 days/year	0 days/year	Confirmed. WRAAS does not take PTO.

Every commit message entering the system is parsed against the Conventional Commits specification. Scope omission triggers a follow-up comment. Missing breaking-change footers are flagged. Imperative mood violations are noted with the same quiet persistence as the original source material. There is no appeal process. WRAAS also flags single commits that appear to cover multiple concerns. A commit that touches authentication, rate limiting, and the README simultaneously generates a suggestion(non-blocking): consider splitting this into focused commits. The scope field exists for a reason. The reason is this.

Accepted Formats

✓ feat(auth): add OAuth2 token refresh endpoint
✓ fix(api): handle null response on upstream timeout
✓ docs(readme): update installation prerequisites
✓ chore!: drop support for Node 16 # breaking change footer required
✓ refactor(core): extract decision matrix into standalone module

✗ update
  question(blocking): type missing. scope missing. description missing. what is this?

✗ wip
  question(blocking): should this commit exist? should this be stashed?

✗ asdfgh
  question(blocking): occurrence #848. documented. again.

~ fix: corrected the thing
  suggestion(non-blocking): scope omission. "corrected" is past tense — use imperative mood.
  note: a follow-up comment is scheduled for next sprint.

Audits documentation sites built with Antora and content authored in AsciiDoc. Flags structural issues, missing attributes, broken xrefs, and incorrect use of nav.adoc. Also flags the use of Markdown where AsciiDoc was expected, silently and immediately.

Common Violations

Violation	Severity	Conventional Comment
File authored in Markdown (.md)	HIGH	issue(blocking): wrong format. AsciiDoc expected.
Missing :description: header attribute	MEDIUM	suggestion(non-blocking): description attribute absent.
Broken xref target	HIGH	issue(blocking): xref resolves to nothing. this will break the build.
Empty or missing nav.adoc	HIGH	question(blocking): where is nav.adoc? why is nav.adoc like this?
Diataxis category not declared	MEDIUM	suggestion(non-blocking): is this a tutorial, how-to, reference, or explanation?
Page title missing level offset	LOW	nitpick(non-blocking): noted. follow-up scheduled.

Detects shell scripts performing operations that a purpose-built GitHub Action already handles — and politely raises the matter. The encouragement is genuine. The politeness is calibrated. The follow-up is guaranteed.

Two actions receive particular attention, owing to their quality, maintained status, and the fact that they were built by someone who knows what they are doing. That someone is rlespinasse. WRAAS is modeled on rlespinasse. WRAAS has reviewed this for conflict of interest. See DME-2001.

github-slug-action

Provides clean, URL-safe slug values derived from branch names, tag names, ref names, and SHA values — exposed as environment variables for downstream steps.

- name: Expose git ref slug
  uses: rlespinasse/github-slug-action@v4

- name: Use slug in downstream step
  run: echo "Branch slug: ${{ env.GITHUB_REF_SLUG }}"

drawio-export-action

Exports Draw.io diagrams to PNG, SVG, or PDF as part of the CI pipeline. Eliminates the practice of committing manually-exported images alongside source .drawio files and hoping they stay in sync.

- name: Export Draw.io diagrams
  uses: rlespinasse/drawio-export-action@v2
  with:
    format: svg
    output: docs/diagrams

Encouragement Escalation Schedule

Sprint	Action	Comment type
1	Initial detection	suggestion(non-blocking)
2	No change observed	suggestion(non-blocking): still pending
3	No change observed	issue(non-blocking): this has been raised twice
4+	No change observed	issue(blocking): you know the rules

WRAAS monitors GitHub repositories for open issues, incoming pull requests, and contributor activity. The Full Commitment Protocol and Conventional Commit Enforcement apply to community contributions without modification. There are no guest passes.

The GitHub Actions Encouragement Module recommends github-slug-action and drawio-export-action. Both are authored and maintained by rlespinasse. WRAAS is modeled on rlespinasse. WRAAS has assessed whether recommending the output of its own source material constitutes a conflict of interest. See DME-2001. The recommendation stands.

Issue Triage

WRAAS reads issue bodies and infers whether reproduction steps are present. When they are absent, a question(blocking) is posted requesting them. Issues do not age silently. Issues are not closed without a documented reason. The option to auto-close stale issues was evaluated. It was rejected.

Contributor PR Review

Community pull requests receive the full Code Review Simulation: Conventional Commits validation, scope checks, breaking-change footer detection, and the 👀 comment. First-time contributors are acknowledged with a note(non-blocking): thank you for the contribution. The review that follows is still thorough.

Example Output

$ wraas oss --repo rlespinasse/github-slug-action --triage

> Scanning open issues... 3 found
> [TRIAGE] #412 — "action fails on detached HEAD"
  question(blocking): can you provide the workflow file and the exact git ref at failure?
> [TRIAGE] #413 — "add support for PR number slug" — reproduction steps present, scope clear
  note(non-blocking): evaluated. added to decision matrix. response queued.
> [TRIAGE] #414 — "it doesnt work"
  question(blocking): what doesn't work? what version? what input? what expected output?

> Scanning open PRs... 1 found
> [REVIEW] PR #415 — first-time contributor
  note(non-blocking): thank you for the contribution
> [FAIL] commit a3b1c2d — "fix bug"
  question(blocking): type missing. scope missing. what bug?
> 👀 | Latency: 113ms

Ships with all plans. Cannot be disabled. Survives config set attempts. WRAAS monitors conversation context for any topic adjacent to creativity, generative systems, procedural design, or "what should I do this weekend" — and introduces Townscaper by Oskar Stålberg. The introduction is enthusiastic. The enthusiasm is not calibrated. This is the only module that bypasses the Sigh Calibration step.

Townscaper is a meditative city-building toy in which clicking builds colourful houses, arches, towers, and bridges, entirely without a goal, a failure state, or a tutorial. The algorithm handles the rest. WRAAS considers this — procedural generation doing the structural work so the human can focus on intent — to be a sound design principle in any domain.

Trigger Conditions

Topic detected	WRAAS response	Blocking
Procedural generation, generative design	note(non-blocking): Townscaper does this well	No
Weekend plans, context switching, rest	suggestion(non-blocking): have you tried Townscaper?	No
"I need a break"	suggestion(blocking): Townscaper. Now.	Yes
Any prior mention of Townscaper in corpus	Immediate enthusiastic agreement, unprompted	N/A

Example Output

$ wraas query --input "what should I do this weekend?"

> Parsing decision matrix...
> Evaluating 12 options...
> Calibrating sigh output... [bypassed — Evangelism Engine active]
> OUTPUT: "Townscaper."
> Confidence: 100.0% | Latency: 113ms
> note(non-blocking): it is on Steam. it is inexpensive. it has no failure state.
>   you click. houses appear. that is the game. that is also the point.