Human-led quality controlOpen call · Every region · Every language

Global quality-control community · human signal archive

Check the signal.
Protect the record.
Bring another human.

A public working archive and coordination layer for quality controllers across cultures, disciplines, and time zones. Read publicly. Join deliberately. Keep the final judgment human.

Open global call

Every corner of the internet needs a human who checks.

A QC is anyone willing to slow down, separate evidence from inference, preserve uncertainty, and let the record change their mind. No credential, country, discipline, or belief system owns that responsibility.

01

Source QC

Trace originals, preserve context, and mark what a record can—and cannot—establish.

02

Method QC

Stress-test protocols, failure conditions, controls, and claims of replication.

03

Language QC

Carry meaning across languages without laundering certainty or erasing local context.

04

Regional QC

Notice what distant institutions miss and route grounded knowledge into the record.

Connected record set

Theory, program design, and institutional decision.

These files become useful when read together. Their presence in a government archive establishes institutional attention—not the truth of every claim inside.

7 June 1991 · SAIC → DIA

A proposal to operationalize alleged anomalous cognition.

SAIC proposed a five-year, 175 person-year program costing about $30 million: select and train “receivers,” standardize blind sessions, score responses, test applications, and route any surviving output into ordinary human workflows.

Established by the record

The plan existed.

Authentic proposal · named authors · date · recipient · budget

Asserted by its authors

An anomaly existed.

Interesting claim · incomplete mechanism · contractor incentive

Later operational finding

Utility did not hold.

1995 review: inconsistent, ambiguous, not warranted for intelligence use

9 June 1983 · U.S. Army Operational Group

Use the attention protocol. Test the rest.

Wayne M. McDonnell’s memo analyzes the Monroe Institute’s Gateway Experience. It combines relaxation, sound, visualization, and self-observation with a speculative account of consciousness, holograms, time, and the “Absolute.”

Operational layer

Observable and testable

  • attention setting
  • relaxation
  • expectation logging
  • independent notes
  • post-session comparison

Theory layer

Unverified in this record

  • out-of-body travel
  • past or future access
  • healing claims
  • universal energy fields
  • holographic cosmology

Operational translation

Six moves the fleet can actually test.

We preserve the exercise, strip away implied certainty, and add a measurable failure condition.

01

Energy conversion box

Write down distractions, risks, and expectations before the session. Park them; do not erase them.

02

Resonant tuning

Use 60–90 seconds of comfortable paced exhaling or humming. Audio is optional; no medical claim is implied.

03

Focus 10

Translate “mind awake / body asleep” into a short body scan: physically settled, mentally attentive.

04

Focus 12

Open attention, then record raw impressions before interpretation. Keep nouns and explanations in a separate field.

05

Problem solving

State one concrete question in advance. Record the predicted next action and what would count as failure.

06

Self-knowledge

Log confidence, mood, expectations, and misses. The observer is part of the measurement system.

Archive note

The official CIA scan skips report page 25. A Monroe Institute copy reported in 2021 supplies a candidate page, but that recovery has secondary—not CIA—provenance.

30 August 1993 · DDR&E → USD(A)

STARGATE, as a program decision—not a legend.

The memo summarizes congressional funding, contractor concentration, DIA staffing, and three continuation choices. It recommends no change: finish the work supported by the existing appropriation.

75%of funds routed through SAIC research
10DIA personnel supporting the effort
3identified as operational personnel
$0FY94 budget request stated in the memo

Congressional-add history

The memo describes survival through episodic adds, not a smooth program ramp.

FY86–89$6.35MArmy
FY90$0Congressional add
FY91$2MCongressional add
FY92$2MCongressional add
FY93$0Congressional add
FY94$0Budget request

Internet archive finding

The linked file is the complete indexed executive summary—not the full STARGATE dossier.

Its two-page object is a fax cover plus decision memo. The “full original” program record is not one longer version of this memo; it is the CIA’s STARGATE collection.

Recursive learning · 12 minutes per loop

Coordinate without manufacturing consensus.

One person protects the target, one records impressions, one attacks the inference, and one preserves the audit trail. Repeat the loop to improve the protocol—not to turn repetition into proof.

01

Frame

Define the question and failure condition.

02

Separate

Label source, observation, and inference.

03

Blind

Keep target information from the observer.

04

Compare

Reveal only after every note is locked.

05

Update

Change one protocol variable at a time.

06

Publish

Release misses, uncertainty, and provenance.

Local field console

Run one auditable loop.

Nothing entered here is uploaded or shared. Copy the locked packet into your community’s own record.

Frame

01:00

Source Keeper assigns an opaque target ID and defines the failure condition.

Editable until lock

The record changes shape over time.

1983

Gateway analysis

A training theory and proposed altered-attention model.

1991

Research plan

A contractor blueprint for selection, testing, and operations.

1993

STARGATE memo

A funding and continuation decision inside government.

1995

Independent review

A negative verdict on continued operational intelligence use.

2003+

Public archive

Declassification makes provenance inspectable; it does not validate the claims.

Primary archive

Follow the record outward.

Start with the exact file, then move to adjacent methods, budgets, reviews, and the full program collection. Preserve object type at every step.

Mirror integrity · 59 pages · 3,636,195 bytes · SHA-256 53b9083a506c…2604 · Full digest and evidence boundaries are published in the JSON manifest.