HOW TO USE ASTRA
A field guide that is ready before the login exists.
Preparation mode now. Access-specific instructions when the evidence arrives.
A useful manual has to do two things at once: help people prepare for a new kind of work, and refuse to invent the controls, endpoints, or limits they cannot yet verify.
CURRENT MODE
Astra is not a public product you can sign into yet.
The public record supports research results and safety updates, not a public ChatGPT route, API recipe, or pricing table.
THE METHOD
Prepare the work before you prompt.
These principles are useful whether the task is a research question, a repository, a dataset, or a long-running agent.
Define success
Write the desired artifact, acceptance test, stop condition, and human approver before the first request.
Budget the search
Set time, token, tool, and cost limits. More trajectory is not the same thing as more evidence.
Checkpoint the state
Record assumptions, open questions, decisions, and artifacts so the work can be resumed or audited.
Verify independently
Use a second pass, a test, a source check, or an expert review. Keep failures visible instead of smoothing them away.
THE GUIDE MAP
Five chapters, two honest states.
Prelaunch copy is actionable now. Launch copy is a prepared slot that stays gated until the required facts are verified.
Access and setup
Needs updatePrepare an account, a verified source checklist, and a safe workspace. No Astra login or API steps are published because none are documented.
Follow the official entry point, record the plan or eligibility gate, and verify the first successful session before adding screenshots or claims.
Requires: public-availability, chatgpt-availability, api-availability
Your first useful task
Needs updateDefine the task, success criteria, stop condition, and human review step before access exists.
Start with a bounded task that has inspectable artifacts and a clear verification path; record the exact configuration.
Requires: model-identifier, tools-and-modalities
Long-horizon work and checkpoints
Needs updatePlan checkpoints, evidence capture, budget limits, and recovery paths for any future long-running session.
Use explicit checkpoints, tool boundaries, and stop conditions; do not treat a long trajectory as proof of correctness.
Requires: context-window, reasoning-controls, rate-limits
Verification and failure recovery
ConfirmedBuild a second-pass review checklist and identify what can be checked mechanically before the product is accessible.
Preserve raw outputs, independent checks, and failure notes. A fluent answer is not a verified result.
Requires: independent-findings, safety-posture
Cost and resource control
Needs updateModel usage scenarios without filling in unknown rates or quotas.
Use the calculator with documented prices, cached-input terms, limits, and a stated workload assumption.
Requires: pricing, rate-limits
USEFUL TODAY
Prepare a first mission without waiting for a brand name.
Use the same discipline on a currently available system, then keep the record portable if Astra becomes accessible.
- Choose a bounded task.Prefer a repository issue, a fixed document set, or a synthetic dataset over an open-ended “do everything” prompt.
- Freeze the inputs.Record the source files, commit, question set, allowed tools, and environment before starting.
- Define the check.Decide what a human, test suite, citation audit, or formal checker will verify.
- Capture the failure.Store what did not work, what was corrected, and whether the conclusion is supported, inconclusive, or blocked.