Low-Context Execution Packet

Use branch stage/d3-04-kos-shachi-foundry.

Start by verifying the known Mac fallback:

test -f /opt/toolchains/dc/kos/environ.sh
. /opt/toolchains/dc/kos/environ.sh
sh-elf-gcc --version | head -1
make -C ops/toolchains/kos-smoke clean all
file ops/toolchains/kos-smoke/*.elf

Before choosing KOS/Shachi build flags or SDK conventions, search the intel DB and cite useful atom IDs:

scripts/intel/query-shachi-atoms.sh search "KOS toolchain"
scripts/intel/query-shachi-atoms.sh search "PVR_CMD_VERTEX"

Then evaluate Pi-native feasibility under:

/mnt/kitchen/collab/d3-tui/toolchains

Probe first, before building:

ssh mehdifarah@100.120.38.37 'uname -m && command -v gcc g++ make git cmake python3 perl texinfo bison flex wget curl patch'
ssh mehdifarah@100.120.38.37 'ls -la /mnt/kitchen/collab/d3-tui/toolchains'

Preferred order:

1. reuse a staged Shachi/POLYGON SDK if it supports Linux ARM64
2. use a prebuilt KOS/dc-chain toolchain if already present
3. build dc-chain natively on Pi only if logs show dependencies and time are reasonable
4. keep Mac KOS as fallback and document exact sync path for build artifacts

docs/KOS_SHACHI_FOUNDRY.md must include:

• chosen build host: Pi, Mac, or both
• exact environment variables
• exact source command
• smoke build command
• smoke ELF output path
• blocker log path if Pi-native failed
• recommended toolchain path for D3-06
• Shachi atom IDs that influenced build/toolchain decisions

Do not spend the session trying many large builds without preserving logs. If dc-chain build fails once, record the failure and produce a conservative fallback.