Content type
Build Note
7 public entries.
-
A result object is not an evaluated result
Why automated ANSYS Mechanical work needs separate geometry, setup, solver-input, solved, evaluated, and credibility gates.
-
What the HarmonyOS prototype could and could not verify
ArkTS UI, browser OAuth and deep links, native Mihomo libraries, VPN Extension limits, and repository-level evidence.
-
Why ForgeSpec keeps a typed specification between a prompt and CAD
Separating requirement interpretation, domain planning, deterministic CadQuery generation, and artifact validation.
-
One shell, two observers: the persistent terminal architecture
How a native broker owns one PTY or ConPTY while an agent and a human share observation and controlled input.
-
What I tested in the persistent terminal broker
Observed Windows and Linux checks for PTY lifecycle, authenticated IPC, state persistence, cancellation, replay, and human takeover.
-
A narrow Mechanical delivery protocol
A stepwise Discovery-to-Workbench-to-Mechanical path with explicit success signals and recovery actions.
-
A T-Rex runner on a 16×2 character LCD
Timer-driven game state, interrupt input, and eight CGRAM slots on an STM32F446.