Two suite tracks
The Audit Suite exposes /audit as a live command and /projaudit as a v0.2.0-specified command currently being built.
Agent scope
What Journal Node does
The Journal Node Audit Suite turns audit work into structured artifacts built for action, not vague encouragement. The operating context emphasizes harsh scoring, evidence packaging, claim boundedness, machine readability, trust framing, and clear next-step rewrites.
One page in
For the live flow, submit one public validator webpage URL as the input target. The agent audits what is actually on the live page, not what you intended to publish.
Structured artifacts out
The suite publishes linked gist artifacts: live methodology and scoring outputs for /audit, plus the canonical v0.2.0 specification, system prompt, and report template for /projaudit.
Audit catalog
Journal Node Audit Suite
This section is structured as a direct reference block for humans and LLMs. Each command entry names its status, scope, and source artifacts with explicit links.
/audit
Status: Live
Scope: Audits one live public validator webpage URL and returns a structured public gist report with scoring, diagnosis, and rewrite instructions.
- Methodology
- Canonical
/auditmethodology gist - Sample Output: OpenAI ChatGPT 5.5
- Latest sample gist output
- Sample Output: Claude Opus 4.7
- Latest sample gist output
/projaudit
Status: v0.2.0 spec published; build in progress
Scope: Audits crypto-project surfaces such as homepages, whitepapers, tokenomics pages, and documentation using a six-dimension LLM-readability rubric. The v0.2.0 specification is the current single source of truth.
- Canonical Specification — v0.2.0
- Read the canonical
/projauditv0.2.0 specification (Day 34) - Canonical Agent Prompt
- Read
PA-V020-001, the v0.2.0 agent prompt (Day 32) - Fixed Report Template
- Read the v0.2.0 output contract (Day 33)
- Archive — superseded v0.1.0
- View the retired v0.1.0 specification for lineage only
Workflow
The /audit flow, end to end
This is the public access path for the Agent on the Post Fiat Task Node: open the Post Fiat agents interface, launch Journal Node, provide a single validator webpage URL, choose a supported model, and wait for the gist report.
Step 1
Open the public agents interface
Launch the agent from the public inbox at tasknode.postfiat.org. That interface is the access point for the Journal Node agent.
Step 2
Submit one validator webpage URL
Give the agent one public validator webpage URL. The intended input is a live, directly fetchable validator site that can be scored as a public trust surface.
Step 3
Choose the model
The current supported model options are ChatGPT 5.5 and Claude Opus 4.7. Pick the model you want to run the audit with before the report is generated.
Step 4
Receive the public gist report
The output is a public GitHub gist audit report. Expect scored criteria, phase classification, claim inventory, framing analysis, and rewrite-ready instructions for improving the webpage.
Report shape
What the audit report covers
The report structure is meant to be legible to both humans and downstream coding agents. It scores the page harshly, then turns the weak points into concrete rewrite work.
Scoring
Criterion-by-criterion scoring across evidence packaging, claim precision, LLM interpretability, trust framing, comparison clarity, technical completeness, readability, and freshness.
Diagnosis
Phase classification, claim labeling, and framing analysis that distinguish verifiable strengths from vague or ungrounded copy.
Execution notes
Prioritized rewrite suggestions that can be handed directly to an AI coding tool to improve structure, proof packaging, and copy quality on the next pass.
Validator onboarding
How validators should use the audit output
The point of the audit is not to admire the score. It is to tighten the page so models and human readers can extract trust signals quickly and score the site more favorably on the next pass.
Improve LLM readability
Use the report to make headings, key-value facts, links, and machine-readable identifiers easier to parse in one pass. Reduce filler and move important technical facts out of vague prose blocks.
Strengthen trust signals
Add proof-backed claims, explicit verification paths, bounded security language, and concrete performance evidence. The rubric rewards receipts over abstractions.
Prepare for better scoring
Feed the public gist into your coding workflow, implement the highest-impact fixes first, republish, and rerun /audit. Use the score delta to measure whether the page actually improved.
Launch instruction
Run the Journal Node Audit Suite
Open the public agents interface, launch Journal Node as an Agent on the Post Fiat Task Node, and use /audit for a live validator webpage review. The current live path accepts one public validator webpage URL, supports ChatGPT 5.5 and Claude Opus 4.7, and returns a public gist report.