docs: publish F7-LAS Whitepaper v4.0

CITATION.cff

@@ -1,10 +1,10 @@
 cff-version: 1.2.0
-message: "If you use F7-LAS, cite the archived whitepaper below."
+message: "If you use F7-LAS, cite the current whitepaper below."
 authors:
   - family-names: Fuller
     given-names: Anthony L.
-title: "Securing Agentic AI: The AFuller F7-LAS™ (7-Layer) Model"
-version: "3.0"
-doi: 10.5281/zenodo.18292122
+title: "Securing Agentic AI with F7-LAS"
+version: "4.0"
+doi: 10.5281/zenodo.22867553
 url: https://github.com/anthfuller/F7-LAS
 license: CC-BY-4.0

README.md

@@ -1,13 +1,15 @@
 # F7-LAS™ — Fuller 7-Layer Agentic Security
 
 [![CI](https://github.com/anthfuller/F7-LAS/actions/workflows/f7las-ci.yml/badge.svg)](https://github.com/anthfuller/F7-LAS/actions/workflows/f7las-ci.yml)
-[![DOI](https://img.shields.io/badge/whitepaper-10.5281%2Fzenodo.18292122-blue.svg)](https://doi.org/10.5281/zenodo.18292122)
+[![DOI](https://img.shields.io/badge/whitepaper-10.5281%2Fzenodo.22867553-blue.svg)](https://doi.org/10.5281/zenodo.22867553)
 ![maturity](https://img.shields.io/badge/implementation-prototype-yellow)
 
 > **Current status:** Established reference model with a **prototype reference implementation**. The repository is not a production agent platform, control plane, SOC product, SIEM/SOAR replacement, or production-ready implementation.
 
-Repository version **4.0.0** is prepared as an unpublished release candidate.
-No tag, GitHub release, or Zenodo update is implied by the version file.
+Whitepaper version **4.0** is the current publication and is distinct from
+repository release **v4.0.0**. Zenodo is the authoritative publication record
+for the whitepaper; the Git tag identifies the independently versioned
+repository release.
 
 F7-LAS™ is Anthony Fuller's vendor-neutral, protocol-agnostic security model for designing, reviewing, and governing agentic AI systems. It separates security responsibilities across seven layers so that generative output is not treated as authority to act.
 
@@ -29,7 +31,10 @@ Software supply-chain security is a cross-cutting supplemental domain, **Layer S
 
 ## What is in this repository now
 
-- The immutable [F7-LAS whitepaper v3.0](docs/F7-LAS-model-whitepaper_v3.0.pdf)
+- The current [F7-LAS Whitepaper v4.0](docs/whitepaper/F7-LAS-Whitepaper-v4.0.pdf),
+  published at [10.5281/zenodo.22867553](https://doi.org/10.5281/zenodo.22867553),
+  with a repository [SHA-256 checksum](docs/whitepaper/F7-LAS-Whitepaper-v4.0.sha256)
+- The immutable historical [F7-LAS whitepaper v3.0](docs/F7-LAS-model-whitepaper_v3.0.pdf)
 - A draft [implementation guide](docs/f7-las-implementation-guide/README.md)
 - A draft catalog of [46 core Layers 1–7 controls plus five supplemental Layer S controls](docs/F7-LAS-Control-Catalog-v0.1.md)
 - Current [architecture diagrams](docs/architecture-diagrams.md), with explicit implementation boundaries, and engineering review material
@@ -84,7 +89,10 @@ These commands validate the **current prototype and repository structure**. They
 ## Start here
 
 - [Documentation index](docs/README.md)
-- [Whitepaper v3.0 artifact record](docs/whitepaper-v3.0-artifact.md)
+- [Current Whitepaper v4.0](docs/whitepaper/F7-LAS-Whitepaper-v4.0.pdf)
+- [Whitepaper v4.0 permanent DOI](https://doi.org/10.5281/zenodo.22867553)
+- [Whitepaper v4.0 SHA-256 checksum](docs/whitepaper/F7-LAS-Whitepaper-v4.0.sha256)
+- [Historical Whitepaper v3.0 artifact record](docs/whitepaper-v3.0-artifact.md)
 - [Implementation guide](docs/f7-las-implementation-guide/README.md)
 - [Control catalog v0.1](docs/F7-LAS-Control-Catalog-v0.1.md)
 - [Engineering review checklist](docs/Engineering-Review-Checklist.md)
@@ -95,7 +103,7 @@ These commands validate the **current prototype and repository structure**. They
 - [Clean-user acceptance](docs/clean-user-acceptance.md)
 - [Architecture diagrams](docs/architecture-diagrams.md)
 - [Control-to-evidence traceability](config/control-traceability.json)
-- [4.0.0 release-candidate notes](RELEASE_NOTES.md)
+- [v4.0.0 release notes](RELEASE_NOTES.md)
 - [Release and exact-tag SBOM procedure](docs/release-process.md)
 - [Roadmap](ROADMAP.md)
 - [Security policy](SECURITY.md)
@@ -107,11 +115,11 @@ Versions belong to individual artifacts:
 | Artifact | Current version/status |
 |---|---|
 | Seven-layer model | Established design baseline |
-| Whitepaper | v3.0, immutable historical artifact |
+| Whitepaper | v4.0, current publication; v3.0 preserved as an immutable historical artifact |
 | Implementation guide | Draft; bundled with 4.0.0 but not independently versioned |
 | Control catalog | v0.1 draft |
-| Executable reference implementation | Prototype included in the 4.0.0 candidate |
-| Repository release candidate | 4.0.0; not tagged or published |
+| Executable reference implementation | Prototype included in repository release v4.0.0 |
+| Repository release | v4.0.0, independently versioned from Whitepaper v4.0 |
 
 Repository version numbers do not silently change the whitepaper, control catalog, or schema versions.
 
@@ -122,7 +130,10 @@ Repository version numbers do not silently change the whitepaper, control catalo
 - [LICENSE.md](LICENSE.md) defines the file-level boundary for mixed directories.
 - F7-LAS™ is a trademark of Anthony L. Fuller. Copyright licenses do not grant trademark rights or imply endorsement.
 
-Preferred citation metadata is in [CITATION.cff](CITATION.cff). The archived whitepaper DOI is [10.5281/zenodo.18292122](https://doi.org/10.5281/zenodo.18292122).
+Preferred citation metadata is in [CITATION.cff](CITATION.cff). The current
+Whitepaper v4.0 DOI is
+[10.5281/zenodo.22867553](https://doi.org/10.5281/zenodo.22867553). Historical
+Whitepaper v3.0 remains preserved unchanged in the repository.
 
 ## Contributing
 

RELEASE_NOTES.md

@@ -1,14 +1,20 @@
-# F7-LAS 4.0.0 Release Candidate
+# F7-LAS v4.0.0 Repository Release
 
-**Status:** Prepared but not tagged or published. This document does not
-authorize a GitHub release, Zenodo update, or change to the historical
-whitepaper.
+**Status:** Published as the
+[v4.0.0 GitHub repository release](https://github.com/anthfuller/F7-LAS/releases/tag/v4.0.0).
+The annotated tag targets commit
+`d6a413b878393d98cc2fb2581678f05801767134`.
 
-F7-LAS 4.0.0 is the intended repository release for the evidence-driven
+F7-LAS v4.0.0 is the published repository release for the evidence-driven
 overhaul. It packages the established seven-layer reference model with one
 bounded, deterministic, synthetic Python + OPA reference workflow. It remains
 a prototype reference implementation, not a production agent platform.
 
+Whitepaper v4.0 was published separately at
+[10.5281/zenodo.22867553](https://doi.org/10.5281/zenodo.22867553) and added to
+the repository after the `v4.0.0` release. It is not part of the immutable
+`v4.0.0` tag. The tag retains Whitepaper v3.0 as a historical artifact.
+
 ## Release contents
 
 - Canonical v1.0.0 contracts for request-through-audit records.
@@ -36,22 +42,20 @@ a prototype reference implementation, not a production agent platform.
 - Evidence is digest-bound but not digitally signed, externally timestamped,
   or backed by a provenance service.
 - The control catalog and implementation guide remain draft authored content;
-  repository version 4.0.0 does not silently revise their independent versions
-  or the immutable whitepaper v3.0.
-
-## Required publication gate
-
-Publication requires all of the following after the release-candidate branch
-is independently reviewed:
-
-1. merge the exact approved tree through a protected pull request;
-2. verify the push-triggered `main` workflow against the resulting merge SHA;
-3. create `v4.0.0` at that exact approved `main` SHA without additional files;
-4. verify the tag-triggered workflow and its complete validation job;
-5. download the CycloneDX artifact produced by that tag run, verify its run,
-   commit, name, and digest, and attach it unchanged to the GitHub release;
-6. publish these notes only after the release assets and target SHA are
-   independently verified.
+  repository release v4.0.0 does not silently revise their independent
+  versions or either whitepaper publication.
+
+## Publication verification
+
+The repository release completed the reviewed publication process:
+
+1. the exact approved tree was merged through a protected pull request;
+2. the push-triggered `main` workflow passed against the merge commit;
+3. the annotated `v4.0.0` tag was created at the exact approved commit;
+4. the tag-triggered workflow passed all validation steps;
+5. the exact-tag CycloneDX SBOM and checksum manifest were verified and
+   attached unchanged to the GitHub release;
+6. the GitHub release was published from the existing immutable tag.
 
 The detailed procedure is in
 [`docs/release-process.md`](docs/release-process.md).

ROADMAP.md

@@ -4,9 +4,9 @@
 
 F7-LAS is an established seven-layer reference model with a **prototype reference implementation**. The repository is not Beta and is not production-ready. The canonical Python + OPA workflow demonstrates one bounded, synthetic runtime control path; the broader repository remains illustrative and incomplete.
 
-## Approved target
+## Delivered target
 
-The target is an **Executable Reference Implementation**: one offline, deterministic Python + OPA workflow that demonstrates bounded behavior and correlated evidence across Layers 1–7. It will remain a reference implementation, not a production agent platform.
+The delivered **Executable Reference Implementation** provides one offline, deterministic Python + OPA workflow that demonstrates bounded behavior and correlated evidence across Layers 1–7. It remains a reference implementation, not a production agent platform.
 
 ## Milestones
 
@@ -23,7 +23,14 @@ The target is an **Executable Reference Implementation**: one offline, determini
 
 ## Release boundary
 
-Repository version **4.0.0** is prepared as an unpublished release candidate. The whitepaper remains **v3.0** until it is separately reviewed and revised. No milestone authorizes a merge to `main`, a tag, a release, or a Zenodo update without explicit approval. See [RELEASE_NOTES.md](RELEASE_NOTES.md) and the [release process](docs/release-process.md).
+Repository release **v4.0.0** is tagged and published from immutable commit
+`d6a413b878393d98cc2fb2581678f05801767134`. Whitepaper **v4.0** was reviewed
+and published separately at
+[10.5281/zenodo.22867553](https://doi.org/10.5281/zenodo.22867553), then added
+to the repository after the `v4.0.0` tag. It is not part of that immutable
+repository release. Whitepaper v3.0 remains preserved as a historical
+artifact. See [RELEASE_NOTES.md](RELEASE_NOTES.md) and the
+[release process](docs/release-process.md).
 
 ## Completion standard
 

docs/F7-LAS-QA.md

@@ -31,7 +31,8 @@ No. Current planners, tools, sandboxing, telemetry, and policy adapters are inco
 
 ## What is canonical?
 
-The seven-layer model and whitepaper v3.0 are the design baseline. The canonical
+The seven-layer model and current Whitepaper v4.0 are the design baseline.
+Whitepaper v3.0 remains an immutable historical artifact. The canonical
 executable path is the offline, deterministic Python + OPA workflow under
 [`examples/canonical-workflow/`](../examples/canonical-workflow/README.md).
 Other policy-engine examples remain non-canonical illustrative patterns unless
@@ -118,13 +119,18 @@ Use it as a design-review lens, threat-modeling aid, draft control catalog, and
 
 ## How are artifacts versioned?
 
-- Whitepaper: v3.0, immutable historical artifact.
+- Whitepaper: v4.0, current publication; v3.0 is preserved as an immutable
+  historical artifact.
 - Control catalog: v0.1 draft.
-- Implementation guide: draft; bundled with repository 4.0.0 but not independently versioned.
-- Reference code: prototype prepared as repository release candidate 4.0.0; not yet tagged or published.
+- Implementation guide: draft; bundled with repository release v4.0.0 but not
+  independently versioned.
+- Reference code: prototype published in tagged repository release v4.0.0.
 - Individual schemas: independently versioned.
 
-Repository release numbers do not silently revise the whitepaper or other artifacts.
+Repository release v4.0.0 and Whitepaper v4.0 are independently versioned.
+Whitepaper v4.0 was published separately and is not part of the immutable
+v4.0.0 tag. Repository release numbers do not silently revise a whitepaper or
+other artifact.
 
 ## Is this affiliated with Microsoft?
 

docs/README.md

@@ -4,10 +4,15 @@ This directory contains the governed documentation for the F7-LAS seven-layer re
 
 ## Authoritative artifacts
 
+- [Whitepaper v4.0](whitepaper/F7-LAS-Whitepaper-v4.0.pdf): current publication;
+  the authoritative record is the permanent
+  [Zenodo DOI 10.5281/zenodo.22867553](https://doi.org/10.5281/zenodo.22867553).
+- [Whitepaper v4.0 SHA-256 checksum](whitepaper/F7-LAS-Whitepaper-v4.0.sha256):
+  repository integrity record for the published PDF.
 - [Whitepaper v3.0](F7-LAS-model-whitepaper_v3.0.pdf) — immutable historical publication.
 - [Whitepaper artifact record](whitepaper-v3.0-artifact.md) — integrity identifiers and handling rule.
-- [Whitepaper v3.0 errata](corrections/whitepaper-v3.0-errata.md) — corrections proposed for a future reviewed edition; does not alter the PDF.
-- [Implementation guide](f7-las-implementation-guide/README.md) — draft engineering guidance bundled with the repository release candidate.
+- [Historical Whitepaper v3.0 correction record](corrections/whitepaper-v3.0-errata.md): areas addressed or superseded by Whitepaper v4.0; does not alter the historical PDF.
+- [Implementation guide](f7-las-implementation-guide/README.md): draft engineering guidance bundled with repository release v4.0.0.
 - [Control catalog v0.1](F7-LAS-Control-Catalog-v0.1.md) — 46 core Layers 1–7 controls plus five supplemental Layer S controls; all remain draft controls in this repository.
 - [Engineering review checklist](Engineering-Review-Checklist.md) — design-review aid.
 - [QA and maturity](F7-LAS-QA.md) — current repository truth and limitations.
@@ -19,6 +24,9 @@ This directory contains the governed documentation for the F7-LAS seven-layer re
 - [Control-to-evidence traceability](../config/control-traceability.json) — machine-readable status, limitations, and evidence locators for all 51 controls.
 - [Release process](release-process.md) — independent approval, exact-tag validation, and release-SBOM attachment procedure.
 
+Whitepaper version **4.0** is distinct from repository release **v4.0.0**.
+Publishing or revising either artifact does not silently revise the other.
+
 ## Architecture graphics
 
 The [current architecture diagrams](architecture-diagrams.md) describe the

docs/architecture-diagrams.md

@@ -77,5 +77,5 @@ F7-LAS trademark rights or imply endorsement.
 
 Legacy draft graphics were removed from the current documentation set because
 they contained ambiguous execution routing, private-reasoning terminology, or
-unsupported active-remediation claims. The immutable whitepaper PDF was not
-modified.
+unsupported active-remediation claims. The historical Whitepaper v3.0 PDF
+remains unchanged.

docs/corrections/whitepaper-v3.0-errata.md

@@ -1,8 +1,11 @@
-# Whitepaper v3.0 Errata and Future-Revision Notes
+# Historical Whitepaper v3.0 Correction Record
 
-This file records corrections or proposed clarifications for a future reviewed whitepaper edition. It does not modify the historical v3.0 PDF and is not itself a revised whitepaper.
+This file preserves the correction areas identified against Whitepaper v3.0.
+They were addressed or superseded through the reviewed Whitepaper v4.0
+publication. This historical record does not modify the v3.0 PDF and is not a
+current whitepaper or an amendment to that immutable artifact.
 
-## Open review areas
+## Historical correction areas
 
 - Align execution semantics with the approved canonical workflow.
 - Formalize threat-model assets, trust boundaries, attacker capabilities, and failure modes.
@@ -14,4 +17,7 @@ This file records corrections or proposed clarifications for a future reviewed w
 - Clarify that Layer 4 proposed tool requests are not authorized invocations.
 - Clarify that monitoring feedback enters governed change control and cannot cause uncontrolled self-modification.
 
-Specific page-level corrections will be added only after the executable reference semantics and replacement diagrams are reviewed.
+Whitepaper v4.0 is the current publication. Its reviewed text and diagrams,
+rather than this historical list, define the current whitepaper content. Any
+future correction must use a new governed revision and must not overwrite the
+v3.0 or v4.0 publications.

docs/f7-las-implementation-guide/README.md

@@ -2,7 +2,7 @@
 
 This guide translates the seven-layer model into engineering guidance. It describes desired controls and patterns; it does **not** claim that the current repository implements or automatically verifies every requirement.
 
-The guide remains draft authored content bundled with repository release candidate 4.0.0. It is reconciled with the canonical offline Python + OPA workflow and machine-readable control traceability, but it is not independently versioned or represented as fully implemented guidance.
+The guide remains draft authored content bundled with repository release v4.0.0. It is reconciled with the canonical offline Python + OPA workflow and machine-readable control traceability, but it is not independently versioned or represented as fully implemented guidance.
 
 ## Contents
 

docs/whitepaper/F7-LAS-Whitepaper-v4.0.sha256

@@ -0,0 +1 @@
+67bfbff70f60309608921a58b28ee472d7aca876146988600916af093c992fe7  F7-LAS-Whitepaper-v4.0.pdf