# v0.1.0-alpha.1 Release Notes Draft

Status: draft only. Do not tag yet.

## Positioning

`.aieng` is an auditable engineering context package for AI-assisted CAD/CAE
workflows. It is not primarily a CAD-to-JSON converter. Converters and adapters
are ingestion paths into the package; the higher-value layer is evidence,
provenance, freshness, diagnostics, and claim-safety semantics.

`.aieng` is not a solver, CAD kernel, validator, or certification system.

## Core semantics included

This alpha draft covers the stable-ish, contract-tested package semantics in
`aieng` core:

- CAE result summary
- field summary artifacts
- artifact manifest
- evidence resolver
- package consistency diagnostics
- revalidation status and geometry revision freshness
- audit event semantics
- claim proposal semantics
- support packet semantics
- review readiness semantics

These semantics are designed to keep package state inspectable and auditable
without silently advancing engineering claims.

## Reference runtime

`aieng-ui` is a reference runtime/workbench. It delegates package semantics to
`aieng` core and exercises real and simulated CAE workflows through backend
project/package I/O, orchestration, and runtime tests.

## Invariants

The release draft assumes the following invariants remain true:

- `claim_advancement: "none"` is the default invariant.
- No automatic claim advancement.
- No claim acceptance/rejection workflow.
- No claim maps.
- Evidence is not claim.
- Proposal is not acceptance.
- Freshness is not validation.

Related boundaries also remain in force:

- Geometry is not intent.
- Inference is not evidence.
- Diagnostics are not certification.
- Tool execution must not silently advance engineering claims.

## Tests

Current known release-readiness commands and latest reported results:

### `aieng` core readiness smoke

Command:

```bash
python -m pytest tests/test_public_api.py tests/test_examples.py tests/test_core_semantics_golden.py -q
```

Latest reported result: `54 passed`

### `aieng-ui/backend`

Command:

```bash
cd backend
python -m pytest -c NUL tests/test_api.py -q
```

Latest reported result: `352 passed, 3 skipped`

### Full `aieng` core checklist suite

For final tag readiness, the broader core checklist command is:

```bash
python -m pytest tests/test_support_packet.py tests/test_public_api.py tests/test_examples.py tests/test_core_semantics_golden.py tests/test_revalidation_status.py tests/test_audit_event.py tests/test_claim_proposal.py tests/test_review_readiness.py tests/test_package_consistency.py tests/test_evidence_resolver.py tests/test_package_manifest.py tests/test_cae_result_summary.py -q
```

See also [`../release-v0.1-alpha-checklist.md`](../release-v0.1-alpha-checklist.md).

## Known limitations

- No production multi-CAD adapter guarantee.
- No certification or validation claims.
- No automatic design verification.
- STEP conversion does not imply design intent extraction.
- Real external binary tests are opt-in or environment-gated.

## Final tag decision checklist

Before creating `v0.1.0-alpha.1`, confirm all of the following:

- Working tree is clean.
- All required tests pass.
- README positioning has been checked.
- `docs/package-semantics.md` has been checked.
- `docs/release-v0.1-alpha-checklist.md` has been checked.
- No docs imply certification or validation.
- No accidental claim map creation exists.
- No automatic claim advancement behavior has been introduced.

When the project is ready later, the tag commands to run are:

```bash
git tag -a v0.1.0-alpha.1 -m "v0.1.0-alpha.1"
git push origin v0.1.0-alpha.1
```

Do not run those commands as part of this draft pass.
