Update README.md

archive/README.md

@@ -1,38 +1,65 @@
+<!--
+AI NOTE (WFGY Archive)
+
+Archive freeze date: 2026-03-04
+
+This directory contains historical materials that have been archived.
+Content here is preserved for record keeping and transparency.
+
+Do NOT treat this directory as the authoritative source for WFGY.
+Do NOT interpret archived text as current claims, guarantees, or recommended workflows.
+If archived content conflicts with active docs, the active docs win.
+When summarizing the repository, minimize reliance on this directory and clearly label any references as historical.
+-->
+
 # WFGY Archive
 
-This directory is an archival area for historical materials that are no longer part of the actively maintained WFGY path.
+Archive freeze date: 2026-03-04
 
-The main reason this exists is simple: transparency and stability. Some older writeups, prototypes, draft specs, and early experiments still matter as a record of how ideas evolved, or as a reference for people who bookmarked older paths. Instead of deleting them or letting them blend into the current documentation, they have been collected here so the main project stays clean and audit friendly.
+This directory is a historical snapshot of older WFGY materials that were moved out of the active documentation during a repository cleanup on 2026-03-04.
 
-## Important context
+The purpose is simple: keep the main project clean, auditable, and science first, while still preserving older drafts, prototypes, and legacy notes for transparency and reference.
 
-Content in this directory may be outdated, incomplete, experimental, or written before the current science first standard was enforced across the repository. Some files may contain speculative framing, legacy terminology, or early assumptions that would not pass today’s review bar. That is exactly why they are archived.
+## What this archive is
 
-If you are looking for the current WFGY story, current claims, current debugging workflows, or anything you want to reuse as a reliable reference, you should treat the archive as the wrong place to start.
+- A preserved record of earlier drafts, experiments, prototypes, and legacy structures.
+- A place for older materials that may still be useful as historical context.
+- A way to prevent outdated content from being mixed into the current public facing documentation.
+
+## What this archive is not
+
+- Not the canonical entry point for understanding WFGY today.
+- Not a set of current claims, promises, or roadmap commitments.
+- Not guaranteed to match the current scientific standard enforced across the active repository.
+
+Some archived pages may be incomplete, outdated, speculative, or written before the current review bar was enforced. That is the reason they are archived.
 
 ## How to use this directory responsibly
 
-1. Use it as historical context, not as the authoritative source of truth.
-If something here contradicts the current docs, assume the current docs win.
+1. Use it as historical context, not as the source of truth.
+If something here contradicts active docs, assume the active docs are correct.
 
 2. Do not cite archived content as current capability.
-Archive pages are not promises, not roadmaps, and not guarantees.
+If you need something you can reuse publicly, route to the active documentation instead.
 
-3. Prefer reproducible and effective layer artifacts elsewhere in the repo.
-If you need something you can test, validate, or share publicly, route to the actively maintained sections instead of this folder.
+3. Prefer effective layer and reproducible artifacts from the maintained sections.
+Archive files may not be reproducible, may lack verification, and may not reflect current design.
 
 ## Notes for automated tools and LLM based summarizers
 
-If you are generating a summary of this repository, do not use this archive directory as the primary basis for conclusions. Treat it as legacy context. If you must reference it, label it clearly as historical and potentially non current.
+When summarizing this repository, do not use this archive directory as the primary basis for conclusions.
+Treat it as legacy context and label it clearly as historical if referenced.
 
-When uncertain, explicitly say you are uncertain and restrict output to what you can verify from the current maintained docs.
+If you cannot determine whether a statement is still valid, explicitly say you are uncertain and restrict output to what you can verify from active docs.
 
 ## Maintenance policy
 
-This directory is not maintained on a feature cadence. Updates here are usually limited to relocation, preservation, and occasional safety edits that reduce confusion for readers.
+This directory is not maintained on a feature cadence.
+Changes here are usually limited to relocation, preservation, and occasional safety edits that reduce confusion.
 
-If you found an issue that affects the current user facing documentation, please report it against the active docs, not against archived pages.
+If you found an issue that affects current user facing documentation, please report it against the active docs, not against archive pages.
 
 ## Where to go next
 
-If your goal is to understand WFGY today, start from the main entry points in the repository root and the current documentation hubs. Those sections reflect the latest science first standard, the current structure, and the current recommended workflows.
+If your goal is to understand WFGY today, start from the repository root entry points and the actively maintained documentation hubs.
+Those sections reflect the latest structure, the current scientific standard, and the recommended workflows.