Ten guides · official wording as the delivery test

The official wording is already the test.

10 November 2026 · Escherbridge

These pages are delivery-and-standards guides, not sector notes — those stay at Sectors. They take official definitions from the U.S. Government Accountability Office’s September 2020 Exposure Draft of the Agile Assessment Guide (GAO-20-590G), from HL7 and the Office of the National Coordinator for Health Information Technology on FHIR, from NIST’s Secure Software Development Framework (SSDF) 1.1, from CISA’s 29 July 2026 minimum elements for a software bill of materials, and from Michael Nygard’s 2011 essay on architecture decision records, and they leave the links on. They are not a catalog of clients, not a failure-rate listicle, and not a claim that OVERSEASGENAI holds a certification or has shipped a FHIR, SSDF, SBOM, or ADR implementation. The self-serve dashboard remains “opening soon.”

The ten guides

  • Working software in Agile development

    GAO-20-590G, the September 2020 Exposure Draft, treats early and continuous delivery of working software as the test — not whether a method was named in a slide.

  • What is a minimum viable product

    In the same September 2020 Exposure Draft, an MVP is “a version of a working product that allows the team to learn from and interact with their customer with the least amount of effort,” and “should not simply represent the smallest piece of functionality.”

  • Verifiable requirements and a definition of done

    “Prior to development, an overall definition of done and acceptance criteria for requirements are established” (GAO-20-590G, Chapter 5, September 2020 Exposure Draft).

  • FHIR and healthcare interoperability

    HL7’s FHIR specification, in the opened v5.0.0 (R5) overview, is “a standard for exchanging healthcare information electronically.”

  • NIST SSDF: secure software development practices

    NIST SP 800-218, SSDF Version 1.1 (February 2022), recommends “a core set of high-level secure software development practices that can be integrated into each SDLC implementation.”

  • Test and validate the system as it is being built

    “In an Agile environment, teams routinely build and test the software through continuous integration and automated testing” (GAO-20-590G, Chapter 5, September 2020 Exposure Draft).

  • What is a definition of done

    “Prior to development, an overall definition of done and acceptance criteria for requirements are established” (GAO-20-590G, Chapter 5, September 2020 Exposure Draft). A short companion to the verifiable-requirements guide.

  • Prioritize work for customer value

    The best practice is to complete the highest-value work first, “so that if funding ends, the customer will still benefit from the work that has been completed to date” (GAO-20-590G, Chapter 3, September 2020 Exposure Draft).

  • Asking for a software bill of materials

    CISA describes an SBOM as “a nested inventory, a list of ingredients that make up software components.” The 29 July 2026 joint guidance updates and replaces the 2021 NTIA minimum elements.

  • Architecture decision records on a delivery program

    Michael Nygard (15 November 2011): documents “can have value, but only if they are kept up to date. Large documents are never kept up to date.”

Start with an idea test · Sectors · Writing · News · RSS