EVIDENCE-DRIVEN IDEA EVOLUTION

Do not just generate proposals.
Make the idea survive questions first.

XMM Proposal Agent is an XMM-Newton research framework. It turns new nearby-galaxy X-ray archive inputs, idea generation and attack, feasibility calculations, and TAC-style non-compensatory judgment into a traceable long-lived evolution line.

01 · ARCHITECTURE

Separate memory, machine, and trace—or a single conversation will masquerade as a scientific process.

The core is not one oversized prompt. It is a set of explicit state boundaries: stable role specifications, accumulating scientific memory, and disposable but auditable execution traces.

THE PROGRAMpipeline/

Role specifications. Changed rarely; they say who may do what and what they must not do.

R0 → R8 + LDistinct survey, proposal, attack, judgment, feasibility, drafting, and TAC-sim responsibilities.
ORCHESTRATOR.mdDefines the role graph, two modes, and stopping rules; one budgeted shift runs at a time.
Fresh shiftsEach role handles one work unit; the next role receives evidence and a handoff, not an earlier agent's long context.
THE MEMORYshared/

Reusable archive coverage, idea ledger, sources, and trust records.

survey/Archive facts become question-linked opportunity tags, not generic target-level conclusions.
ideas/Lineage, relative ranking, lifecycle, and graveyard survive across cycles; a killed idea remains knowledge.
TRUST_TABLEInstrument and archival facts carry sources, status, and applicability boundaries; model memory is not a substitute.
THE TRACEcycles/ · runs/

Materials, attacks, rebuttals, calculations, and handoffs from every round.

cycles/Default evolution-mode trace: new input, forks, kills, R6-lite, and portfolio decisions.
runs/AO-triggered proposal-run artifacts: archive check, feasibility, draft, and panel review.
3-line handoffEvery shift leaves did / found / next. The next role receives evidence, not an impression.

The critical separation: shared memory is not silently rewritten by one failed run, and a run cannot redefine the role rules that it relies on. tools/ is a separate calculators layer for reproducible feasibility and provenance commands; it does not decide scientific state.

ARCHITECTURE POSTER

Make role separation, evidence flow, and independent review visible in one frame.

This conceptual poster treats the system as an observatory made of distinct stations. Materials, archive facts, ideas, calculations, and drafts may travel only along a trace-preserving rail; no one role skips every check.

  • 01

    Cyan and lime rails depict the traceable flow of evidence packets, shared memory, and did / found / next handoffs.

  • 02

    The red station is the R4 red-team: it stress-tests the blueprint rather than finding better wording for it.

  • 03

    The branching gate and round table represent R5 portfolio decisions and the R8 TAC-sim panel.

This is an architecture concept, not an execution record. Concrete scientific state, proposal lifecycle, and source-verified facts remain in the repository's canonical records.

02 · TWO MODES

Evolution is the steady state. Drafting a proposal is an event with entry conditions.

This prevents the reversed workflow of choosing a topic first and searching for reasons later. The system maintains a portfolio repeatedly filtered by evidence and critique; only a mature idea enters a formal proposal run.

DEFAULT · CONTINUOUS

EVOLUTION

Start from a new archive, literature, or human-annotation input; generate, challenge, sanity-check, and re-rank ideas. Without new input, the loop legally stops at STAGNATION rather than spending tokens remixing old material.

M0 discoverR0 verifyR2 proposeR3 / R4R6-liteR5 portfolio
AO-TRIGGERED · BOUNDED

PROPOSAL RUN

Begin only with a proposal-ready idea. An ObsID-level archive check and the R6-full feasibility chain come first; when numbers do not close, R5 may only narrow or replace the objective. R8 TAC-sim then grades the draft against an explicit rubric.

R1 archiveR6-fullR5 judgeR7 draftR8 TAC-sim
03 · SAFEGUARDS

The point is not to make an agent sound more certain. It is to make errors earlier, cheaper, and harder to hide.

The framework separates an attractive idea from an idea that has survived review. Attacks, eliminations, and unresolved empirical questions are not concealed; they become explicit inputs to the next cycle or a future proposal's deepening plan.

INPUT DISCIPLINE

No new evidence, no new cycle

A new round must consume new external information, a verified archive record, or an explicit human annotation. Stopping is an informative state, not a failure.

FRESH CONTEXTS

The generator does not judge itself

R2 proposer, R4 red-team, and R5 judge are distinct fresh shifts. Independence is more than a new label: it prevents end-to-end attachment.

ADVERSARIAL BINS

FATAL / REFRAME / EMPIRICAL

Logical or physical fatal problems, salvageable framing failures, and questions that require new data enter different downstream paths.

NON-COMPENSATORY

One poor dimension cannot disappear into an average

R5: any single poor axis can block promotion. R8: only when two or more reviewers assign poor to the same dimension is a draft returned for revision.

04 · ROLE SYSTEM

Every consequential judgment has a responsible role—and a boundary it must not cross.

Roles are not ceremony. They separate retrieval, evidence verification, scientific imagination, adversarial review, numerical closure, and writing so that an error has an identifiable source and repair point.

M0

Material Collector

Discovers public candidate material; it contributes discovered leads, not source-verified truth.

DISCOVERY ≠ TRUST
R0

Surveyor

Turns multi-observatory archive facts into reusable coverage and opportunity records.

ARCHIVE → MAP
R1

Librarian

Performs source and ObsID-level archive work for one question, preventing a duplication narrative.

QUESTION → FACTS
R2

Proposer

Builds baseline ideas and forks from verified opportunities and questions, not invented evidence.

OPPORTUNITY → IDEA
R3

Analyst

Gathers evidence for and against an idea, preserving unknowns and the data needed to resolve them.

IDEA → EVIDENCE
R4

Red-team

Attacks duplication, observatory fit, decisiveness, physics, and cost as an XMM TAC referee would.

IDEA → KILL SHOTS
R5

Judge

Manages the portfolio; it kills, parks, forks, or promotes under explicit axes and min-gates rather than average impressions.

EVIDENCE → STATE
R6

Feasibility

Turns model → count rate → pileup → background → exposure into an inspectable technical chain.

CLAIM → NUMBERS
R7

Drafter

Organizes the closed evidence-and-feasibility record into an XMM AO structured draft.

RECORD → DRAFT
R8

TAC-sim Panel

Uses different reviewers and the science merit / appropriate use of XMM / observational realizability / completeness & clarity rubric to grade the draft and route concrete revisions.

DRAFT → REVIEW
L

Tutor

Turns unclear instrument and method concepts into learnable, testable explanations so the human remains able to judge.

UNKNOWN → LEARNING
05 · CLAIM BOUNDARY

This is a research framework—not a promise that entering a topic returns a funded proposal.

A public page may explain the design, but it must not package a design aspiration as a validated scientific conclusion. Project mechanisms have Trusted, Provisional, and Questioned states. Proposal lifecycle, instrument facts, and any specific scientific result remain authoritative only in their respective canonical records.

  • It does not promise funding, proposal quality, or any scientific discovery.
  • It does not represent M0 search output or model memory as source-verified evidence.
  • It does not make a dashboard or promotional page authoritative for idea lifecycle state.
  • It does not bypass actual AO submission: the researcher remains responsible for final submission and scientific accountability.
A DIFFERENT STARTING POINT

Move from “what can we write?” to
“what is worth continuing?”

For an XMM proposal, scarce value is not wording. It is a scientific opportunity that remains after archive checks, counterarguments, feasibility, and panel judgment.

Return to the framework