WFGY 4.0 is not a single page. It is a family of connected surfaces.
This page helps readers understand how the major WFGY 4.0 documents fit together.
Some pages explain the global engine view. Some pages go deeper into route-first diagnosis. Some pages explain legitimacy-first governance. Some pages expose the runtime constitution. Others show evidence, demo strategy, or raw experimental records.
This page exists so readers do not have to guess where to go next.
What it is: the flagship landing page for WFGY 4.0
Use it when: you want the global framing first
Twin Atlas is the engine-level view of the WFGY 4.0 family. It explains why route-first orientation, legitimacy-first governance, and advisory-only coupling belong together in one system.
What it is: the route-first detailed surface
Use it when: you want the practical diagnosis side first
Forward Atlas is the Twin Atlas engine name for Troubleshooting Atlas / Problem Map 3.0. This is the practical route-first surface for structural troubleshooting, broken invariant localization, neighboring-route separation, and first repair direction discipline.
What it is: the legitimacy-first detailed surface
Use it when: you want the governance side first
Inverse Atlas is the detailed surface for authorization, repair legality, lawful downgrade, emission ceiling, and the question that matters most under pressure: whether the current answer has actually earned the right to exist that strongly yet.
What it is: the entry point into the inspectable Twin Atlas constitution
Use it when: you want to see the engine skeleton directly
This is where readers should go if they want the runtime-facing view of the system rather than the landing-page framing.
What it is: the full Twin Atlas engine constitution
Use it when: you want the actual structural laws, state logic, and output contract
This is the deepest technical surface in the public release. It exposes the route-first, bridge, governance, state, and seal layers in inspectable form.
What it is: the entry point into the coupling layer
Use it when: you want to understand why Forward Atlas and Inverse Atlas cannot simply be placed side by side
Bridge is not a cosmetic middle layer. It exists because conceptual pairing is not the same thing as lawful operational handoff.
What it is: the core Bridge rationale page
Use it when: you want the shortest high-level explanation of what Bridge prevents
This page explains why route plausibility can leak into authorization if the system has no disciplined coupling membrane.
What it is: the evidence entry point for WFGY 4.0
Use it when: you want the public proof side first
This page explains what the evidence section is actually measuring, why it is not a generic benchmark, and how the current public evidence is organized.
What it is: the fastest public before/after scoreboard
Use it when: you want the shortest answer to “what changed?”
This is the best page for readers who want to understand the current directional results quickly.
What it is: the protocol surface
Use it when: you want to understand how the governance stress test is designed
What it is: the fast reproducible demo path
Use it when: you want the shortest 60-second public demo surface
What it is: the cleaner protocol path
Use it when: you want stronger separation and a more blackhat-resistant structure
What it is: the strongest story-level examples
Use it when: you want the most legible case cards for public understanding
What it is: the honesty page for the evidence layer
Use it when: you want to know what the current evidence does and does not prove
What they are: model-specific text records of experiment outputs
Use them when: you want to inspect the raw model-level records directly
These raw TXT files are not presented as a formal universal benchmark archive. They are public experiment records and transparency assets. Their role is to show what the prompts and outputs looked like in concrete runs, not to replace cleaner reruns or future protocol refinement.
Readers should treat these files as:
- raw experiment records
- prompt-visible artifacts
- model-specific before/after traces
- reproducibility helpers
The safest interpretation is still: read the summary, inspect the raw runs, and rerun if you want independent confirmation.
What they are: official visual surfaces for the release
Use them when: you want hero graphics, scoreboards, or case visuals
What they are: public-facing demo surfaces
Use them when: you want the story-level and reproducible demonstration layer instead of the full protocol
- Twin Atlas README
- Evidence Hub
- Results Summary
- Troubleshooting Atlas or Inverse Atlas
- Twin Atlas README
- Troubleshooting Atlas
- Bridge README
- Results Summary
- Twin Atlas README
- Inverse Atlas
- Runtime README
- Methodology Boundary
- Twin Atlas README
- Runtime README
- Runtime Constitution
- Bridge Contract
- Seal and Audit