Research roadmap

A twelve-month plan. Bars show intended windows. Status is planned, in progress or done. No venue names are listed.

Agenda status (plan counts)

Bar lengths are counts of programs, roadmap items and planned artifacts marked planned, in progress or done. These are agenda counts, not measured results.

Click a status to highlight matching plan rows. Counts are agenda status, not measurements.

Status: Planned (pattern), In progress (accent border), Done (filled).

View as table
Agenda status (plan counts)
StatusCount
Planned12
In progress7
Done0

Twelve-month roadmap

Horizontal bars mark intended start and end months on a 0 to 12 scale. Status labels sit beside each bar, not inside it. Status comes from the data file.

0 to 3 months | 3 to 6 months | 6 to 12 months

AI-Pass submission

Route

0 to 2 months · In progress
In progress

0 to 2 months · In progress

Quality orchestration charter and shared invoice benchmark

Assure

0 to 3 months · Planned
Planned

0 to 3 months · Planned

Simulation baseline with fault injection (ROS 2, Gazebo)

Physical

0 to 3 months · Planned
Planned

0 to 3 months · Planned

Graph-pruning study

Ground

3 to 6 months · Planned
Planned

3 to 6 months · Planned

First quality-routing results

Assure

3 to 6 months · Planned
Planned

3 to 6 months · Planned

Sovra raw data and scoping

Foundation

0 to 3 months · In progress
In progress

0 to 3 months · In progress

Degradation curves and verification methodology note

Physical

3 to 6 months · Planned
Planned

3 to 6 months · Planned

Integrated pipeline paper

Route

6 to 12 months · Planned
Planned

6 to 12 months · Planned

Open benchmark for extraction or orchestration under constraint

Foundation

6 to 12 months · Planned
Planned

6 to 12 months · Planned

Status: Planned (pattern), In progress (accent border), Done (filled).

View as table
Twelve-month roadmap
ItemProgramMonthsStatus
AI-Pass submissionRoute0 to 2In progress
Quality orchestration charter and shared invoice benchmarkAssure0 to 3Planned
Simulation baseline with fault injection (ROS 2, Gazebo)Physical0 to 3Planned
Graph-pruning studyGround3 to 6Planned
First quality-routing resultsAssure3 to 6Planned
Sovra raw data and scopingFoundation0 to 3In progress
Degradation curves and verification methodology notePhysical3 to 6Planned
Integrated pipeline paperRoute6 to 12Planned
Open benchmark for extraction or orchestration under constraintFoundation6 to 12Planned

Publication stage gates

Work moves through scoping, data and log review, draft, internal referee-style review, then submission. Counts are shown only when items exist.

Publication stage gates

Publication pipeline: Scoping, Data and logs reviewed, Draft, Internal referee-style review, Submission. Venue names are not listed.

  1. 1

    Scoping

    No items in this stage yet.

  2. 2

    Data and logs reviewed

    No items in this stage yet.

  3. 3

    Draft

    No items in this stage yet.

  4. 4

    Internal referee-style review

    No items in this stage yet.

  5. 5

    Submission

    No items in this stage yet.

View as table
Publication stage gates
StageCount
ScopingNo items in this stage yet.
Data and logs reviewedNo items in this stage yet.
DraftNo items in this stage yet.
Internal referee-style reviewNo items in this stage yet.
SubmissionNo items in this stage yet.

Planned artifact releases

  • AI-Pass submission package (protocol and logs)RouteIn progressIn progress
  • Sovra scoping notes and raw data release planFoundationIn progressIn progress
  • Quality orchestration charterAssurePlannedPlanned
  • Graph-pruning study packageGroundPlannedPlanned
  • Simulation baseline with fault-injection protocolPhysicalPlannedPlanned

Qualitative risks

Qualitative risk map

Qualitative 3 by 3 map of likelihood versus impact. Levels are low, medium and high. No probabilities.

Likelihood: Low
Likelihood: Medium
Likelihood: High
Impact: High
  • Safety overclaim
  • Dual-use drift
  • Dependence on student labor
  • Benchmark credibility
  • Overclaimed service levels
.
Impact: Medium
.
.
  • Spread across too many tracks
Impact: Low
.
.
.
View as table
Qualitative risk map
RiskLikelihoodImpactMitigation
Dependence on student laborMediumHighTwo people per program, documented pipelines
Spread across too many tracksHighMediumOne lead per track, small physical track
Benchmark credibilityMediumHighIndependent adjudication, disclosed construction
Overclaimed service levelsMediumHighState assumptions explicitly
Safety overclaimLowHighName the testbed stage for every claim
Dual-use driftLowHighWritten policy before any public release