Alpha Saint Phoenix Trust & Security Methodology

Research Status / Methodology

Every sentence has a status.

The site is only as trustworthy as the difference it keeps between what was seen, what is suspected, what is proposed, and what the public record already supports.

Claim tiering

How to read a line of ASP research

Status language on this site is deliberate. If a page does not mark a claim, treat it as context, not as an established result.

StatusMeaning
ObservedWhat Alpha Saint Phoenix directly documented.
CorrelatedA pattern repeatedly seen, without established causation.
HypothesizedA possible explanation for observations.
ProposedA theoretical mechanism, framework, or architecture.
Externally supportedA claim supported by published third-party evidence.
ExperimentalWork still under observation or testing.
EstablishedUsed only when the support is strong enough to warrant the word.
Work status

What the publication labels mean

Manuscripts and frameworks on the public site carry a status so that “exists” is not mistaken for “released.”

In Development Internal Research Under Review Prepublication Public Archived Protected Research
Method

How the work is done

Longitudinal observation

Study behavior across time where the phenomenon cannot be understood from an isolated exchange. Longitudinal observation does not, by itself, establish causality. It changes the observational lens.

Cross-model comparison

Compare recurring patterns across different systems and model generations where that comparison is warranted.

Evidence preservation

Keep source records, chronology, research notes, and developmental history rather than collapsing the file into the latest interpretation.

Claim tiering

Separate direct observation from interpretation, hypothesis, architecture, and external evidence.

Recursive analysis

Study feedback among context, memory, interaction, behavior, and the next system state.

Interdisciplinary interpretation

Read technical behavior alongside human factors, cognition, communication, trust, and systems design.

Correction & revision

Preserve meaningful contradictions and failed hypotheses rather than silently rewriting research history.

Phenomenology before ontology

Describe the observable pattern and its chronology first. Interpretive claims about what the pattern “is” remain separate, and are marked as such.

Record

Provenance of the research itself

A visitor should be able to tell earlier work from later claims. Dated chronology, version history, and archived source references are maintained internally. Public chronology is published only from verified records.

Where ASP research intersects peer-reviewed literature, technical reports, or established safety and governance work, that evidence is cited and distinguished from ASP observation. Citations are not ornamental. They must support the sentence they sit beside.

Private longitudinal conversational archives, where they exist, are disclosed only as protected research materials. Raw conversations are not published by default.