Governance Log

Review Notices

A governed log for baseline registrations, queued amendments, and staged review thresholds across the public record.

This page exists so canonical change can be named, scoped, and challenged in public rather than drifting through quiet edits or implied authority.

Classification Formal review and amendment log
Notices 4
Access Public record

Open the notice register Read the charter Open the JSON route

Review File

FFTAC-RVW-01

Authority Tracks baseline, queued, and staged review notices so canonical change cannot hide inside silent drift

Baseline notices 1

Review Cycle Updated whenever a formal notice is registered, queued, or retired

No silent drift. No hidden canon. No theatrical amendment theater.

Change Control

Review Notices

This file keeps canonical change visible so the Foundation cannot revise itself by quiet drift.

What Counts As A Review Notice

A review notice is the public marker used when the Foundation registers a baseline, names an upcoming amendment threshold, or stages a governance review around a surface that is still expanding. It is not a performance of bureaucratic gravity. It is a restraint against silent revision.

Why This Page Exists

The charter already states that the first formal review should eventually appear as FFTAC-REC-01. This page gives that promise an actual operating home before the first amendment cycle arrives.

Current Prelaunch Posture

The founding public edition is treated as a named baseline rather than an invisible default.
The first full-cycle review remains queued until the atlas, briefing layer, and journal rhythm have actually matured.
Further review candidates may be staged in advance when exports, AI boundaries, moderation, or participation layers are likely to harden into long-term public policy.

Editorial Rule

Routine typo fixes and presentational cleanup do not need amendment theater. Material shifts in doctrine, standards, public authority, atlas posture, or interactive boundaries do need a review trail that can be cited, challenged, and revisited later.

Baseline

1

Registered starting points against which future public amendments should be compared.

Queued

1

Named formal reviews that still need their threshold conditions met before issuance.

Affected records

12

Distinct record IDs already named inside the review trail so later changes can cite exact targets.

Notice Register

Notice register

Each notice names the trigger, affected record scope, and next action required before the public file changes in a material way.

Launch baseline

Founding public edition registered as the baseline record

Registers the current launch-era public edition as the comparison point for future amendments, corrections, and promoted research changes.

Trigger Initial governed public release of the Foundation record.

Scope Manifesto, charter, standards, research atlas, recovery routes, journal shell, and launch discovery infrastructure.

Active baseline during prelaunch buildout.

Next action: Use this baseline whenever a later notice needs to describe what changed and why.

Open notice anchor Inspect the charter

Full-cycle review

First formal review after the initial atlas, briefing, and archive cycle

The first formal review will record what changed once the institution completes one outward cycle of atlas expansion, signals briefings, and durable journal releases.

Trigger Completion of the first full cycle named in the charter.

Scope Canonical doctrine, publication promotion rules, and the threshold for moving mature research into the official record.

Queued; the threshold has been named publicly but not yet satisfied.

Next action: Issue a notice that cites the baseline, names affected files, and explains each adopted revision in plain language.

Open notice anchor Inspect the publication queue

Atlas governance

Atlas scope, provenance, and export posture review

Before the atlas is treated as a wider reusable research substrate, its record IDs, source trails, export formats, and attribution guidance should be reviewed as one governed package.

Trigger Wider external reuse of atlas record IDs, CSV exports, and machine-readable route discovery.

Scope Research Program, generated export routes, provenance notes, Downloads discovery, and the HTML Site Map feed layer.

Staged while exports and focused record views continue to expand.

Next action: Decide whether future exports, mirrors, or manifests need stronger versioning than the current launch surface.

Open notice anchor Open the export desk

Interactive governance

AI boundary, summit moderation, and live-discussion review

If the AI Engine, digital summits, or protected discussion surfaces expand, their boundaries should be reviewed together so the institution does not loosen machine and moderation posture by accident.

Trigger Expansion of live programming, moderated discussion, or deeper AI-assisted public workflows.

Scope AI Engine constraints, community rules, summit moderation, contact routing, and participation boundaries for future live exchange.

Staged until outward programming and discussion layers widen.

Next action: Publish any boundary changes before scaling interactive channels beyond the current launch posture.

Open notice anchor Inspect the standards

Review Discipline

Review discipline

These rules keep the log legible enough for researchers, skeptics, and future contributors to audit how the institution changes.

No silent drift

Material shifts in doctrine, standards, atlas posture, or institutional boundaries should be named in the log instead of being smuggled through quiet rewrites.

Name the affected records

Each notice should point back to the exact public files, record IDs, or routes that would be touched if the review matures into a formal change.

Keep corrections proportional

Typos and housekeeping can be corrected routinely, but anything that changes public meaning, authority, or boundary-setting belongs in the notice system.

Leave a machine-readable trail

The review log should remain linkable, searchable, and exportable enough that outside researchers can follow the governance trail without reverse-engineering screenshots or rumors.

Affected Record Map

Affected public records

Canonical files, atlas routes, and publication layers already named inside the review queue so later amendments can cite precise targets instead of vague institutional mood.

FFTAC-AI-01 / Linked notices: 1 AI Engine

Bounded AI system for adversarial reframing

FFTAC-COM-01 / Linked notices: 1 Community Guidelines

Sets the conduct and moderation posture for public comments, summits, submissions, AI-assisted contributions, and protected exchange

FFTAC-CNT-01 / Linked notices: 1 Contact

Routes launch-facing questions, research corrections, recovery orientation, and media requests into the right working lane

FFTAC-DWN-01 / Linked notices: 1 Downloads

Public downloads for posters, wallpapers, seal files, press materials, and supplemental symbolic study assets

FFTAC-STD-01 / Linked notices: 2 Editorial Standards

Controls tone, method, and AI boundaries

FFTAC-CHR-01 / Linked notices: 2 Institutional Charter

Defines scope, authority, and boundaries

FFTAC-ACC-01 / Linked notices: 1 Join

Explains voluntary pathways into the institution

FFTAC-JRN-01 / Linked notices: 2 Journal

Live archive for essays and transmissions

FFTAC-MAN-01 / Linked notices: 2 Manifesto

Foundational public declaration

FFTAC-RCV-01 / Linked notices: 1 Recovery Guide

Public guide for readers leaving fear-based religion and rebuilding judgment without replacement dogma

FFTAC-RSR-01 / Linked notices: 2 Research Program

Comparative archive, claim index, and active program of inquiry

FFTAC-SMP-01 / Linked notices: 2 Site Map

Provides a governed human-readable map of the public record, participation lanes, and machine-readable feeds

Section Index

Notice register
Review discipline
Affected record map

Reference File

Publication Links

Participation

Quick Routes

Machine route

governance/review-notices

Use the JSON route when you want the same notice state for indexing, external analysis, or tooling without scraping the page layout.

Open the route

Public Assurances

Voluntary participation remains primary
Critique remains institutional
AI remains bounded by editorial governance