Browse / Agent tools
Particle-Academy/fancy-template
Document templates for the Fancy document writers: a writer document with {{ tokens }} and JSON directives plus a declaration of the data it needs. Sandboxed, bounded, no code execution. One spec, three runtimes, one conformance table.
Works.Tested on 2026-10-27. From the README alone, on Linux with Haiku.

What we checked
Does it run from the README?Yes. Running in 7:43 on a clean Linux box.The run
Tested Oct 27, 2026, rev af965c9.
Does it do what the README says?3 of 3 claims held up.Evidence
“The three legs pass the same 203 conformance rows”
Expected 203/203 rows match on each leg. Got 203/203 = 100.0%.
“Three legs produce byte-identical output”
Expected all three legs equal. Got 3 legs equal.
“Realistic example templates render identically across legs”
Expected 211/211 rows equal across the three legs. Got 211/211 = 100.0%.
Which checks were skipped?2 checks skipped.Reasons
Skipped checks count as neither passes nor failures.
Examples: 2 skipped
- Sabotage harness breaks every bound (documented): Not run: scripts/sabotage.py reads envelope sibling checkouts (repos/fancy-expr, writer repos) that do not exist in this VM; AGENTS.md says it runs from inside the envelope only.
- Writer read-back of corpus (documented): Not run: --writers needs the nine writer repo checkouts of the envelope (AGENTS.md); not present. Plain parity run was executed instead via the probe.
Which setups did we try?Works with Haiku.Setups
Linux / Haiku: works, Oct 27, rev af965c9.
Needs keys, a login or a browser?No.Details
None seen
Is it safe to run?No unexpected network or file activity found in these checksWhat we saw
No problems traced to this repository code in these checks; a short run cannot prove safety. 6 static matches retained as context.
Reviewed as expected for a test run: attempted writes that failed, so nothing was written.
Full event, path and process lists for each observed setup:
A quiet run is not a safety guarantee.
Is it maintained?Maintained · 11 commits in 90 days · 0 merged PRs in 90 days · 0 open issues · 0 open PRsActivity
actively maintained: last commit 0 days ago; 11 commits and 0 merged PRs in 90 days; 0 open issues, 0 open PRs; latest release 2026-10-27
Can I show this on my README?Copy the badge.Badge
The run
Oct 27 · rev af965c9Independent test, not endorsed by the project.