INTERNAL AGENCY // OUTER COMMS

SIMULATION // MAINNET HOLD // NO CEREMONY TIME ACTIVE

PREFLIGHT
STANDBY.

STARLIGHT // SIGNAL ACQUIRED
STARLIGHT :: LAUNCH TERMINALPUBLIC BUILD / NO WALLET CONNECTION REQUIRED

INTERNAL AGENCY PRESENTS

STAR
ASCENT.

A signal for people who refuse to sleepwalk through the age of artificial intelligence. STAR ASCENT is the first opening in the wall.

Read the token disclosure ↓

● GENESIS // UNSCHEDULED · MAINNET HOLD

REPLACEMENT UTC WINDOW · NOT PUBLISHEDNO CEREMONY TIME IS ACTIVE · NO AUTOMATIC TRANSACTIONS.
GENESIS EVENTUNSCHEDULED · MAINNET HOLDBROADCAST · CODE PUBLIC // EVIDENCE HOLD
THE SIGNAL IS OPEN // BUILD THE STRANGE // BUILD THE BEAUTIFUL // BUILD IN PUBLIC // STAR ASCENT

LOCAL INTERFACE // NO WALLET REQUIRED

STEER THE SIGNAL.

Move through the field. The constellation answers. This is a visual transmission only—no wallet, account, or data connection occurs here.
INTERACTION IS LOCAL TO THIS SCREEN

TRANSMISSION // 001

THE SIGNAL IS OPEN.

[01] Internal Agency is opening its first public chapter.

[02] The proposed IAT reward contract is public, not active.

[03] Mainnet stays on HOLD until code, funding, review, and evidence match.

OUTER COMMS // SECURE

THE SIGNAL
IS ALIVE.

A constellation answers from the black. One room. One rising ship. Every line is moving.

GENESIS // COMMAND CENTER

CHOOSE YOUR
ENTRY VECTOR.

Three public surfaces. One verification order.
01 // CANONICAL RECORDOPEN THE DOSSIERRead the public record, token design target, and evidence gates.↗02 // READ THE CHAINOPEN IAT NETWORKInspect Solana, player wallets, IAT positions, rewards, and CCC state from one read-only screen.↗03 // WITNESSBROADCAST WINDOWThe window opens exactly; transaction execution remains human-approved.↓
Amber STAR ASCENT signal-acquired deep-space telemetry artwork
PRE-LAUNCH ART · Decorative brand artwork — not live telemetry or network status.
PAWS, a fictional golden kitten, chasing a prismatic light across a dark star floorPAWS // PRISM SCOUT

NIGHTFLIGHT // VISUAL EDITORIAL

THE SIGNAL FOUR.
IN FULL SPECTRUM.

Four fictional adult women, four distinct looks, one playful Nightflight scene.

The second frame places AI ECE's rainbow knee-high costume beside an inert, non-operational RPG-shaped studio prop. It is editorial set dressing, not equipment.

ENTER THE NIGHTFLIGHT PREVIEW ↗
Ellie, Radiance, AI ECE, and Alia, four fictional adult women age 25 or older, wearing distinct fully clothed iridescent, gold, emerald, and red couture in a glass atrium while PAWS crosses the floor
THE SIGNAL FOUR // RAINBOW ATRIUM // PAWS ON THE FLOOR
AI ECE, a fictional adult woman age 25 or older, in fully clothed emerald-and-black couture and rainbow knee-high socks, holding an inert, non-operational RPG-shaped studio prop in a design workshop
AI ECE // RAINBOW KNEE-HIGH COSTUME STUDY // INERT STUDIO PROP

SCORPION GENERATION // LAUNCH CONTROL

WE DO NOT
WAIT FOR THE
FUTURE.

The stage is a ship. The signal is a gathering. The ascent is ours.
Adult Scorpion Generation stage director and light operators at a starship launch-rave control deck

THE CREW // ARRIVAL WINDOW

THE LIGHTS
ARE ALREADY
ON.

Not a promise. A scene set for the people arriving with their eyes open.
Adult stage commander and light operators in a red spacecraft launch hangar
A crew witnessing the STAR ASCENT launch beneath a luminous constellation

THE SCORPION GENERATION

WE DON'T WATCH
THE FUTURE.

We gather at the edge of the signal: artists, operators, believers and night people. The ship rises; the room becomes a constellation.

THE TRANSMISSION

The future is not handed down.
It is taken back.

Internal Agency is a living experiment in collective imagination, technology, culture, and self-determination. STAR ASCENT is our first broadcast: an invitation to build the strange, the beautiful, and the useful in public.

$IAT / SOLANA

A signal.
A gathering.

SUPPLY DESIGN TARGET1,000,000,000 IAT
NETWORKSolana
PRESALENone
REWARD CONTRACTPROPOSED / HOLD

B3 is the main architecture and retains the V2 economic feature set published at /tokenomics. The official mint, law program, optional Privacy Vault, reward router, and authority evidence are not yet published; the program is not active. Read the complete proposed terms →

TOKEN DISCLOSURE

Design targets are not live facts.

No $IAT token has been presented as live on this page. These fields separate the intended configuration from evidence that must be published before distribution.

Mint addressPENDING
Not published. Treat every address as unofficial until it matches the website and livestream.
Initial supplyPENDING
Design target: 1,000,000,000 IAT. The final on-chain supply must be independently verifiable.
Mint / freeze authorityPENDING
Revocation is planned after the documented initial mint; current status is not yet verified. On-chain evidence must be linked here.
Allocation and releasePENDING
The 50/20/15/10/5 allocation, 400M ordered reward reserve, vesting schedules, annual reward rates, weekly CCC Wildcard, and universal one-roll tiebreak are published as a proposal. Their on-chain implementation and evidence remain pending.
IAT-wide lockdown lawPENDING
Every protocol-local day has a 1% selection chance, except Friday at 66.67%. A selected day closes state-changing IAT actions for 24 hours, from 00:01 to 00:01 in fixed UTC+03:00. The design uses Solana-provided time and a lagged ancestor slot hash, not an external oracle; the result is publicly replayable but is not a bias-resistant threshold VRF.
Optional transfer privacyPENDING
Default IAT transfers remain public. The B3 Privacy Vault is an optional shielded path; its implementation, Devnet evidence, and measured user cost remain pending.

Distribution and reward activation must not begin while any launch-critical implementation or evidence remains pending. Review the publication gate ↓

PUBLICATION GATE

Evidence required before distribution.

A launch announcement is not proof. Distribution stays paused until one public packet makes every critical claim independently checkable.

  1. Final token configuration

    Mint address, token program, decimals, total supply, and a UTC verification timestamp.

    NOT YET PUBLISHED

  2. Authority evidence

    Direct explorer links showing the current mint and freeze authority state; plans or screenshots are not sufficient.

    NOT YET PUBLISHED

  3. Allocation map

    Recipient categories, percentages, token amounts, labeled public wallets, and a mathematical total of 100%.

    NOT YET PUBLISHED

  4. Release controls

    Vesting, lock, custody, and release terms plus the public method for reporting every distribution.

    NOT YET PUBLISHED

Each field remains pending until the linked evidence is live and consistent across the website, pinned announcement, and livestream.

Open English evidence-checklist record

TECHNICAL TEST GATE · LOCAL ONLY

What the allocation validator proves — and what it cannot.

The archived scaffold describes checks for a proposed public allocation manifest without connecting to Solana, a wallet, or a signing service.

  1. Exact arithmetic

    Supply, category totals, and recipient totals must match exactly in integer base units.

  2. Unique identifiers

    Category IDs and public recipient-wallet identifiers cannot be duplicated.

  3. Canonical inputs

    Amounts must be positive whole-number strings, avoiding floating-point rounding.

  4. Deterministic result

    The same manifest produces the same summary and errors in local tests.

LIMIT A passing result only shows that the draft manifest is internally consistent. It does not prove token authenticity, authority state, audit approval, deployment, or safety.

Open allocation-control context

Authority plans stay proposed until the evidence is public.

A second offline scaffold checks that mint and freeze authority intentions are unique, explicit, evidence-gated, and still marked as proposed.

EVIDENCE GATE It does not inspect Solana or prove that an authority is retained, transferred, or revoked. Distribution remains blocked until linked public evidence is independently reviewed.

Open authority-map context

PUBLIC DOCUMENTS

Read the design before any wallet action.

These pre-launch documents describe intended safeguards and unresolved fields. They are not proof that a token exists, that an allocation is final, or that any authority has been changed.

B3 ARCHITECTURE · HOLDOpen retained IAT economic policy (V2)CANONICAL DOSSIER CONTEXTOpen English litepaper recordCANONICAL DOSSIER CONTEXTOpen English evidence-checklist recordCANONICAL DOSSIER CONTEXTOpen English technical-specification recordCANONICAL DOSSIER CONTEXTOpen allocation-control contextCANONICAL DOSSIER CONTEXTOpen authority-map contextCANONICAL DOSSIER CONTEXTOpen English communications-kit recordCANONICAL DOSSIER CONTEXTOpen English rehearsal-playbook recordHOLDOpen English readiness-scorecard recordCANONICAL DOSSIER CONTEXTOpen English incident-response recordCANONICAL DOSSIER CONTEXTOpen readiness-review contextHOLD UNTIL EXACT MATCHOpen release-readiness contextHOLD ON ANY GAPOpen Genesis-evidence contextHOLD · NOT LAUNCH APPROVALOpen readiness-snapshot contextHOLD AFTER EVERY REHEARSALOpen Genesis-rehearsal contextANY CHANGE RETURNS HOLDOpen change-control contextHUMAN DECISION PENDINGOpen launch-handoff context

These links open canonical Dossier context, not executable downloads or preserved validator bytes. Every launch-critical field remains HOLD until backed by linked public evidence.

OPEN THE DEEP ARCHIVEOperational controls, rehearsal and readiness material

PUBLICATION QA · LOCAL ONLY

Files, links, and critical warnings must travel together.

ARCHIVE RECORD · REVIEW HOLD

The archive records a historical local checklist. The current release publishes canonical English fallback only; no target-language copy is approved without source-bound human review.

LIMIT This archive does not certify the current file set, public reachability, evidence freshness, translation approval, or launch readiness. Readiness remains HOLD.

Open readiness-review context

CROSS-CHANNEL RELEASE PACKET · LOCAL ONLY

One source. Three public surfaces. No silent substitutions.

HOLD UNTIL EXACT MATCH

Before any address publication, the website, pinned announcement, and livestream must carry the same launch-critical values character for character.

  1. Website

    Set the canonical public wording here first; unresolved token fields stay PENDING.

  2. Pinned announcement

    Copy the same full values and safety notice without shortening addresses or changing status language.

  3. Livestream

    Display and read back the same values; a verbal claim or cropped screen is not a substitute for public evidence.

LIMIT The archived validator record compares supplied text only. It does not fetch URLs, inspect Solana, verify evidence, handle wallet data, or approve launch readiness. A match still returns HOLD.

Open release-readiness context

EVIDENCE FRESHNESS LEDGER · LOCAL ONLY

Current evidence needs an expiry, two reviewers, and a direct link.

HOLD ON ANY GAP

The archived validator record describes six required evidence checks at one declared UTC time. Missing, stale, future-dated, duplicated, or single-reviewer evidence fails closed.

  1. Six required records

    Token identity, mint authority, freeze authority, allocation, release controls, and channel consistency must each be present.

  2. Explicit freshness window

    Every verified record needs checked-at and expires-at UTC times; stale evidence is rejected deterministically.

  3. Separated review

    A primary and independent review role must be named, and they cannot be the same role.

LIMIT The validator reads supplied metadata only. It does not fetch a URL, inspect Solana, authenticate evidence, handle wallet data, or approve launch readiness. Every result remains HOLD.

Open Genesis-evidence context

COMPOSITE READINESS SNAPSHOT · LOCAL ONLY

Three gates. One fail-closed snapshot.

HOLD · NOT LAUNCH APPROVAL

The archived composer record joins the publication audit, cross-channel packet result, and evidence-freshness ledger result into one deterministic handoff.

  1. Publication integrity

    All public files and critical pre-launch warnings must pass the local publication audit.

  2. Cross-channel consistency

    Website, pinned announcement, and livestream values must match, with unresolved critical fields counted.

  3. Evidence freshness

    The six required evidence records must reconcile as current or unresolved under separated review.

LIMIT The snapshot composes supplied local results only. It does not fetch public links, authenticate evidence, inspect Solana, handle wallet data, or turn a HOLD into READY.

Open readiness-snapshot context

REHEARSAL TRACE · LOCAL ONLY

Timed checks need an auditable handoff.

HOLD AFTER EVERY REHEARSAL

The archived validator record requires three ordered rehearsal records with UTC times, separated operator and reviewer roles, and explicit notes.

  1. T−60

    Record evidence freshness, public-link availability, and cross-channel copy before final staging.

  2. T−15

    Repeat safety, account-control, and support-route checks without introducing new launch claims.

  3. PRE-ACTION

    Recheck immediately before address publication, registration opening, or any scheduled broadcast action.

LIMIT A complete rehearsal trace is operational evidence, not launch approval. HOLD or FAIL remains unresolved, and even three PASS records return HOLD for human review.

Open Genesis-rehearsal context

CHANGE-FREEZE MANIFEST · LOCAL ONLY

Freeze the reviewed bundle. Detect every silent change.

ANY CHANGE RETURNS HOLD

The archived validator record describes SHA-256 digests for an approved public asset inventory and rejection of missing, altered, duplicated, or unexpected files.

  1. Approved inventory

    A reviewer supplies the exact public files intended for the freeze; the tool does not decide which content is approved.

  2. Content digests

    Every frozen file receives a deterministic SHA-256 digest so text changes are visible before publication.

  3. Strict comparison

    Missing, changed, duplicate, or extra files fail closed and require a new human review.

LIMIT The validator reads only supplied local files. It does not fetch the website, authenticate evidence, inspect Solana, handle wallet data, or approve launch readiness. A matching bundle still returns HOLD.

Open change-control context

HUMAN LAUNCH HANDOFF · LOCAL ONLY

Package the evidence. Keep the final decision human.

HUMAN DECISION PENDING

The archived validator record composes the readiness snapshot, rehearsal trace, and change-freeze result into one role-separated handoff packet.

  1. Three supplied results

    Readiness, rehearsal, and frozen-asset results must each remain HOLD and declare that no network was checked.

  2. Separated role codes

    Use only release-operator, safety-reviewer, and decision-owner; names and email addresses are rejected.

  3. Explicit unresolved count

    Pending evidence, release fields, and rehearsal checks are totaled without converting them into a readiness score.

LIMIT The packet records a review boundary; it does not fetch evidence, inspect Solana, handle wallet data, or sign for a person. Software cannot set READY or grant launch approval.

Open launch-handoff context

LAUNCH READINESS · NOT APPROVED

Current readiness: HOLD.

HOLD

Rehearsal materials exist, but launch approval requires current public evidence. A completed draft, passing local test, or previous review cannot replace that evidence.

  1. Token identity

    Mint address, token program, decimals, supply, and verification time are not yet published as one checkable record.

    HOLD

  2. Authority state

    Direct explorer evidence for current mint and freeze authorities is not yet linked and independently reviewed.

    HOLD

  3. Allocation controls

    The final 100% allocation map, labeled public wallets, and release terms are not yet published.

    HOLD

  4. Channel consistency

    The website, pinned announcement, and livestream must be compared after final content is live.

    HOLD

Freshness is a launch gate.

Every evidence record needs a UTC checked-at time, a named review role, and a direct public link. Recheck at T−60 minutes and immediately before any address publication or registration opening. A missing timestamp, unavailable link, changed value, or cross-channel mismatch returns the launch to HOLD.

No numerical readiness score is shown while launch-critical evidence is missing; a percentage could imply approval that has not been earned.

INCIDENT RESPONSE · PUBLIC PROTOCOL

If a launch signal conflicts, stop the action.

HOLD ON ANY TRIGGER

A mismatched address, unexpected wallet request, impersonation report, unavailable evidence link, or changed authority value immediately returns launch activity to HOLD.

  1. PAUSE

    Stop address publication, registration opening, distribution, and scheduled social posts. Do not improvise a replacement address or link.

  2. CONTAIN

    Remove unsafe links from project-controlled surfaces, preserve public evidence, and warn the community without repeating a suspicious wallet or payment request.

  3. CORRECT

    Publish one timestamped canonical correction on this website first, then mirror only approved, source-bound wording to the pinned announcement and livestream.

  4. REVIEW

    Two separated review roles must recheck the full value, direct public evidence, UTC time, and cross-channel match before any activity resumes.

Support will not resolve an incident through a private message and will never ask for a seed phrase, private key, password, personal data, payment, or token transfer.

Open English incident-response record

LAUNCH STATUS

Launch information draft published // Mainnet HOLD
Mint address not published yet
No wallet connection required

OPEN-SOURCE EXECUTION WINDOW

Public code. Physical approval. Verifiable evidence.

The prior ceremony window has expired and no replacement UTC time is published. The source is public now. No transaction is automatic, and mainnet remains on HOLD until funding and every evidence gate pass.

  1. Replacement UTC window pending

    Publish one new exact time only after funding is confirmed and before every bound release artifact is regenerated.

  2. B3 law + retained V2 features

    The B3 law adapter and every retained V2 feature must be built, deployed unfunded, initialized, funded, and exercised on Devnet before any Mainnet decision can be considered.

  3. Mainnet decision

    The signer and verifier may proceed only if metadata, destinations, locks, digests, and handoff records all match.

  4. Registration opens

    Use the on-page status—not a direct message—to confirm availability.

REVIEW THE OPEN-SOURCE B3 CODE ↗

STAGED RELEASE

01

GENESIS

Launch disclosure, livestream, and operator registration.

02

DISTRIBUTION

Publish campaign methodology and the community allocation process.

03

IA PREVIEW

Release announced IA experiences when ready for public use.

POST-GENESIS // INACTIVE PREVIEWS

THE NEXT ROOMS
ARE TAKING SHAPE.

Predictive Engine target: 30 days after $IAT Genesis. Casino DLC target: 15 days after $IAT Genesis. Separate audits, separate activation, no wager route today.ENTER THE FUTURE-SYSTEMS PREVIEW →

OPERATOR FAQ

Where is the official token address?

The official mint address will appear only here, in the pinned official announcement, and on the launch livestream.

Do I need to connect a wallet now?

No. Registration and staking are not open. Never share a seed phrase or private key.

Is IAT an investment promise?

No token price, profit, or guaranteed market value is promised. Proposed reward rates are contract rules for accepted, fully collateralized positions and are not active.

What should a registration signature ask me to do?

Registration should request only a human-readable wallet message. If the wallet asks you to approve a transaction, token access, spending permission, or a transfer, cancel and return to this page independently.

Where will allocation and authority details be published?

The allocation method, distribution rules, recipient categories, and mint/freeze authority status will be documented publicly before distribution begins. Until then, treat those details as pending—not implied.

Does a B3 lockdown stop Solana?

No. It is an IAT-wide protocol law, not a Solana-wide pause. On a selected day, state-changing IAT actions close for 24 hours from 00:01 to 00:01 in fixed UTC+03:00; read-only IAT views and the rest of Solana continue normally.

Can support recover or verify my wallet?

No. Official support will never ask to recover, import, verify, or inspect your wallet, and cannot reverse a transfer. Anyone requesting wallet secrets or payment is impersonating the project.

ANTI-SCAM PROTOCOL

Pause before you sign.

Treat every direct message, countdown, and copied address as unverified until it matches this page and the livestream screen.

STOP

Do not act on urgency, giveaways, presales, support DMs, or “verification” payments.

VERIFY

Match the full address character-for-character in two official surfaces. A logo or display name proves nothing.

PROTECT

Never enter a seed phrase or private key. Reject unexpected signatures and inspect the wallet prompt.

REPORT

Capture the account and URL, report them on the platform, then return here independently—do not follow their link.

There is no private sale, paid registration, support wallet, or secret early-access link.

OPERATOR PROTOCOL

Verify. Sign. Enter.

Registration is free. No seed phrase, private key, password, or payment is ever required.