Changelog · Living workflows

Product revisions, dated and specific.

Each workflow package focuses on methods that can survive a provider or model change. This page records what changed, what still holds, and which revised agentic workflow and knowledge-book files were actually made available through Gumroad.

How the workflows stay useful

A stable method, dated revisions, and a public record.

Layer 1 · Method

The method

Failure taxonomies, LLM-as-judge patterns, RUBRIC scoring, statistical confidence, the prompt hierarchy. These patterns do not change merely because a provider ships a new model, but they are corrected when evidence shows that they should change.

Changed only when the evidence changes
Layer 2 · Revision

What changed, dated

When a revision is published, it is issued as a complete dated file through Gumroad. Material changes are recorded on this page only after the buyer-visible file is verified, with the publication date and affected products.

Review dates are recorded when review work occurs
Layer 3 · This page

The public record

Published revisions are listed with the date and the products they touched. If an earlier entry is wrong, the correction is stated explicitly.

Updated when a revised product file is published

Update log

Newest first. Entries distinguish shipped product revisions from corrections to earlier marketing copy.

2026-08-06

Every field guide rebuilt: numbering, edition data and conflicting update language

Content did not change. The typesetting did, and three of these were visible to anyone who had already paid.

Chapter numbering was off by one in both the Testing Non-Deterministic AI and the AI Security Testing series. The front matter was being counted as Chapter 1, so every real chapter carried the wrong number, in the text and in the table of contents. Fixed in all six field guides. Several chapters also carried hand-written section numbers on top of the generated ones, which rendered as "2.2 1.1" in the contents. Those are gone.

Conflicting update language was identified. The copyright page said updates were "planned", another banner said "free updates for life", and an earlier terms version said "quarterly". The 2026-08-06 build attempted to replace those statements with a twice-yearly cadence and a five-year bundle period. That wording is recorded here as historical context, not as a current sales promise. This changelog does not state a guaranteed update cadence; terms attached to a purchase must be checked on the current product page, checkout and Terms pages.

Edition dates no longer follow the clock. The template stamped the current year, so a field guide rebuilt in 2027 would have claimed to be a 2027 first edition. The date is now fixed to the actual publication date.

Also corrected: the site advertised a founding price ending 31 July 2026 for six days after that date had passed while the price had not moved. The claim is gone rather than left to expire quietly.

2026-07-23

Living workflow system established

No chapter content changed today. What went live was this public changelog and an operating cadence for recording revisions. A reusable appendix template was also created, but it was not included in the shipped field guides. Later copy that implied the appendix already existed in every product was incorrect and has been removed.

Future revisions are recorded here with the affected product, the review date, and the exact change only after the revised file is buyer-visible. Delivery follows the terms attached to the purchase.

All 15 field guides Free lead magnet Historical setup entry

Current edition, by product

This table records the latest mapped agentic workflow package and knowledge-book edition for each paid workflow path. Revision dates change only after the replacement file is available to buyers.

AI-Native QA - Series 1

Next review: not scheduled publicly
Workflow pathLevelStatusLink
Test Failure Triage Workflow L1 START Original edition Gumroad →
AI Application Evaluation Workflow L2 UNDERSTAND Original edition Gumroad →
AI Test Automation Workflow L3 APPLY Original edition Gumroad →
Enterprise AI Testing Operating Blueprint L4 SCALE Original edition Gumroad →
Complete AI-Native QA Bundle Bundle Original edition Gumroad →

AI Evaluation & Reliability - Series 2

Package rows read back · buyer proof open
Workflow pathLevelStatusAvailability
Initial LLM Test Checklist Agentic Workflow L1 START Package row read back Review on Gumroad →Buyer download proof NOT_RUN
Non-Deterministic Evaluation Design Agentic Workflow L2 UNDERSTAND Package row read back Review on Gumroad →Buyer download proof NOT_RUN
Production AI Evaluation System Agentic Workflow L3 APPLY Package row read back Review on Gumroad →Buyer download proof NOT_RUN
Enterprise Evaluation Platform Blueprint Agentic Workflow L4 SCALE Package row read back Review on Gumroad →Buyer download proof NOT_RUN
Non-Deterministic Evaluation Agentic Workflow Path Bundle Package row read back Review on Gumroad →Buyer download proof NOT_RUN

AI-Assisted Security - Series 3

Package rows read back · buyer proof open
Workflow pathLevelStatusAvailability
Authorized Prompt Injection Review Agentic Workflow L1 START Package row read back Review on Gumroad →Buyer download proof NOT_RUN
LLM Security Review Agentic Workflow L2 UNDERSTAND Package row read back Review on Gumroad →Buyer download proof NOT_RUN
AI Security Test Implementation Agentic Workflow L3 APPLY Package row read back Review on Gumroad →Buyer download proof NOT_RUN
Enterprise AI Security Framework Agentic Workflow L4 SCALE Package row read back Review on Gumroad →Buyer download proof NOT_RUN
Authorized AI Security Agentic Workflow Path Bundle Package row read back Review on Gumroad →Buyer download proof NOT_RUN

Questions about updates

Do I have to buy the workflow again to get an update?

When a revision is made available for your edition, access it through the original Gumroad Library entry under the terms attached to the purchase. Use the latest dated file and contact hello@nobrainer.tech if more than one version appears.

What counts as an update worth logging?

A product-file change that affects accuracy, examples, compatibility, or the recommended workflow. Marketing-only edits are not product revisions.

What if a scheduled review finds nothing to change?

The review date is recorded without inventing a product update. A stable method is useful only when the review itself is real.

Does the core method ever get rewritten?

Not merely for a model release. If evidence shows that a method is wrong, the guide is corrected and the change is disclosed here.