Local A/B review

Work A is the older simple terminal landing page. Work B is the April 23 proof-first revamp before today's terminal rewrite.

Dr. RAGnos proof lab

One scan that leaves evidence, fixes, and a reviewer handoff.

Dr. RAGnos turns a messy codebase pass into terminal output, structured JSON, vaulted-secret notes, and an agent-ready next step. The proof viewer is the first artifact, not a product shelf.

Scan walkthrough Request scan walkthrough

Next: terminal, report.json, payload.json, reviewer handoff

Sample scan proof viewer

The artifact is the product.

A credible pass has more than a pass/fail badge. It has the command output, structured reports, an agent payload, and a human reviewer packet visible together.

terminal

$ dr-ragnos scan ./workspace --proof

target redacted-service/ 284 files, 5 scanners

before grade D-minus 41 known CVEs, 16 exposed secrets

after grade A 0 known CVEs, 16 secrets vaulted

wrote .dr-ragnos/report.json

wrote .dr-ragnos/payload.json

handoff ready 5 hours from first scan

terminal

scan output

report.json

release scorecard

payload.json

agent payload

reviewer handoff

human signoff

terminal

scan output

$ dr-ragnos scan ./workspace --proof
grade: D-minus -> A
cves: 41 -> 0
secrets: 16 vaulted
handoff: .dr-ragnos/reviewer-handoff.md

report.json

release scorecard

{
  "grade_before": "D-minus",
  "grade_after": "A",
  "critical_findings_closed": 9,
  "known_cves_remaining": 0
}

payload.json

agent payload

{
  "next_agent": "dependency-cleanup",
  "owned_paths": ["package.json", "src/auth"],
  "constraints": ["vaulted secrets only"],
  "ready_for_review": true
}

reviewer handoff

human signoff

Reviewer packet
- diff summary and remaining risk
- vaulted secret inventory
- reproduction command
- evidence links for every closed item

This sample is static, but the shape is intentional: every finding stays attached to evidence, machine-readable context, and a reviewer-friendly narrative.

Anonymized proof band

A messy release became a shippable handoff.

The sample viewer above mirrors a real cleanup pattern: diagnose the risk, vault what should never have lived in code, remove the known exposure, and leave a reviewer-ready trail.

Release grade

D-minus to A

Risk score rebuilt from scanner findings, dependency fixes, and reviewer signoff.

Known CVEs

41 to 0

Dependency exposure collapsed into a clean release gate.

Secrets vaulted

0 to 16

Hardcoded credentials moved into the vault with rotation notes attached.

Time to handoff

Open ended to 5 hours

Report, payload, and reviewer notes were ready in the same working session.

RAGnos universe

The work band around Dr. RAGnos.

RAGnos spans proof-first audits, agent-native implementation, editorial operating memory, and the loops that keep systems from drifting back.

Proof labs

Run focused scans, close the visible risk, and leave an evidence packet that another operator can trust.

Agent-Native Systems

Build workflows where agents receive scoped payloads, constraints, and reviewer context instead of vague prompts.

Editorial field notes

Turn the proof trail into readable operating memory without letting narrative replace the underlying artifacts.

Loops and drift control

Keep the release surface watched after the first cleanup pass so regressions become routed work, not ambient worry.

Field Notes proof

The writeup stays attached to the artifact trail.

Field Notes are not generic thought pieces. They are edited proof records: what was found, what changed, and what the next operator should trust.

Evidence linked Reviewer ready

From D-minus to A without losing the audit trail

A Field Note can cite the terminal pass, the report JSON, and the reviewer handoff without copying raw logs into the story. The result is editorial enough to read and concrete enough to act on.

What changed in the system

Which evidence moved the decision

What an agent or reviewer should do next

Loops

RAGnos Loops

Start with Dr. RAGnos now. Add the monitoring layer when ongoing drift matters more than one cleanup pass.

Monitor

Watch the code and process changes that matter before release review.

Diagnose

Turn fresh drift into an explainable issue instead of another Slack thread.

Route

Let automation handle routine fixes and keep the human decisions obvious.

Request a scan walkthrough

Share the system context you can safely describe. We will use the first conversation to map whether Dr. RAGnos is a fit.