# PLN-0001 — observed delivery evidence

Date: 2026-11-13. Host: Darwin 27.2.0 arm64 (macOS ARM64).
Toolchain: SDKMAN 25.5.5.0+3-graalce, GraalVM CE 25.5.5.0.3,
JDK 25.0.5.0.3, Gradle Wrapper 9.3.1. Java release target 25, no previews.

## Source identity and authority

Work: WRK-0001. Plan: PLN-0001. Accepted scope: DEC-0001 and DEC-0002.
Implementation request: DSC-0038; scoped repository authorization: DSC-0039.
Git HEAD: c84bb8d36f88ef249a249cdfe7b476fd148717af, with uncommitted changes.
This is not a claim that the implementation was committed at that revision.
ART-0004 records SHA-256 for 80 source/test/resource/build/documentation files,
including new untracked files; it excludes mutable Work bookkeeping.
Manifest SHA-256: 16c28e25e909adff4260e5a41e0ae86fc30b78ed9e8a9c06f380ba70114107b6.

## Executed commands and outcomes

```sh
./gradlew clean test bootJar nativeCompile --console=plain
./gradlew test bootJar nativeDistZip nativeDistTar -PtargetPlatform=macos-arm64 --console=plain
```

Both builds succeeded with JAVA_HOME/GRAALVM_HOME selecting the pinned SDKMAN JDK.
The packaging command was repeated after the final experiment documentation update:
tests/nativeCompile were up-to-date and both archives were regenerated successfully.
JUnit XML totals: 13 suites, 70 tests, 0 failures, 0 errors, 0 skipped (ART-0003).
Modulith verified ten modules. JAR and Spring AOT tasks passed.
Native compilation passed. Seven upstream deprecation warnings and build-time
SLF4J no-provider notices were observed; there were no compilation failures.

Four acceptance tests initially failed because commands were missing (ART-0002).
Later failures exposed an overly broad prose assertion and unsafe-directory validation
occurring after RUN publication. Both were corrected and all 70 tests passed twice.
A final value guard rejects duplicate proposed disposition evidence before application.

The executable alone was copied outside its build directory and exercised with:

```sh
JAVA_HOME=/nonexistent GRAALVM_HOME=/nonexistent \
PATH=/usr/bin:/bin:/usr/sbin:/sbin AIE_KEEP_FIXTURE=1 \
bash scripts/native-smoke.sh /temporary/path/ai-engineering
```

The smoke passed again against the final compiled executable extracted from ZIP.
TAR had identical executable bytes and ran --version with the same absent-JVM setup.
Both archives preserve executable permissions. The repackaged final archives were
extracted again: executable bytes match the exercised binary, and experiment docs
match the canonical source. No adjacent helper libraries were copied or required.
Plain/refinement smoke sections additionally remove Git from PATH.

## Verified behavior

- Topics/surveys persist within their Work; old files remain readable without rewrite.
- Questions include suggestions and free text; recommendation does not supply an answer.
- Guided answers, multiple selections, UTF-8 files and revised answers preserve history.
- Two deterministic adapters resume context through independent JVM/native processes.
- Specific activity routing wins; unconfigured activities use general.
- Invalid adapter output, unsafe paths, wrong ownership and tampered evidence fail safely.
- Synthetic analysis archives/restores proposals with policy, reason and ART evidence.
- A resulting DEC remains DRAFT; adapters create no human approval.
- Completed request replay does not rewrite the Work; changed input is rejected.
- A new observation makes a stored summary stale without invoking an adapter.
- Markdown/JSON context is stable across fresh nested-directory executions.
- Existing no-Git, root Git, multi-Git and operational closure/reopen scenarios pass.
- This project's onboarding refresh preserves root AGENTS.md bytes.
- Final project/Work structural validation returned valid=true with no issues.

Retained final native fixture:
/var/folders/0t/tfsqc14j5wbgh9h4s4dytwb00000gq/T/ai-engineering-smoke.ZUUcyU
Its refinement child holds the two-topic/two-adapter experiment; its root holds
independent runtime/studio Git repositories and the completed/reopened Work scenario.
The fixture is disposable and does not claim real game/rendering measurements.

## Native artifact SHA-256

ai-engineering:
ab7894e1124b8f3624d36124af944c34e2864e12e7cc7e4e80d37d8b56e6d734

ai-engineering-0.1.0-macos-arm64.zip:
9f5a431146463b0fdf785bbdabfa1d52bf310d44c90838df974b5ed590d60fe9

ai-engineering-0.1.0-macos-arm64.tar.gz:
03e92d94eb1cc28e831b347927169c36342f7b68026dc641d2a227a030750a8d

## Limits and next experiment

Only deterministic fixture adapters are implemented. No real provider/model API,
credentials, EPIC propagation, importer or autonomous repository execution is added.
Other native platforms/CI were not executed. Files publish atomically per file;
interrupted cross-record application requires deliberate inspection/repair.
No Zelda files were changed. Work closure remains subject to explicit human review;
implementation authority is not an invented delivery approval.

Next experiment: have a human use survey ask on a real bounded discussion, then
select the first real adapter transport and test its permission/failure boundaries.
