Skip to content

Δ7 — Extend the run-record with usage fields (record-don't-enforce) #41

Description

@jack-champagne

C0. Extend the harmoniqs-main-table PutItem/UpdateItem beyond {task_id, filename, instanceId, taskSize, task_status, timeStamp} to add {submitter, est_profile, wall_seconds, peak_RAM, instance_class, solver, integrator, knots}. No quotas/billing — this is the cheap seam that makes compute-credits a later reporting layer (closes Q153) and the calibration dataset for the real estimator (per solver×integrator).

Acceptance (TDD): a completed run's record has non-null submitter, wall_seconds, instance_class, and the {solver, integrator} it ran.

Gate: blocked by the wk-3 freeze — run-dir contract + SchemaPackage v0 (amicode #15 + the #28–31 stack). RemoteExecutor/the S3 layout is the run-dir contract, so do not start until that lands.

📄 Refs: Spec armonissima/specs/spec-20260628-amicode-cloud-solve-service.md (Δ7) · phased plan §5a (plan-20260603-124231-amicode-phased-build) · aws-infra/INFRASTRUCTURE.mdThe Analysis Pipeline (reuse step_function/ec2_launch_template/dynamodb/runner_image).

Evolve, not build — a working v0 (the aws-infra Analysis Pipeline) already does size→S/M/L EC2→julia→S3→email→terminate. Validate on staging (mirrors prod), then two-step promote.

🏗 Implementation repo: aws-infra (Terraform / lambda / Image Builder). Infra-side reference: harmoniqs/aws-infra#130.

Metadata

Metadata

Labels

enhancementNew feature or requesttrack:cloudTrack C — company compute / cloud solve-service

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions