Add Goose as a design reference for compile-time bounds and verified storage

[0thernet]

Adds Goose (reviewed 2026-10-08) to docs/lineage.md in the same form as the Temper entry, and two candidate items to the north star's programming-language inspiration section:

• Compile-time resource bounds: derive an upper bound on fuel and intermediate bytes for algal.expr.v1 programs before admission (the grammar already admits no unbounded loop) and carry it on the interface. Runtime fuel and byte checks stay authoritative. Adopt only if the bound is sound on every fixture/foundry case and within 10x of observed use on most.
• Verified compact storage: measure a derived, verified-on-load binary form of large stored payloads and history pages against canonical JSON, which stays the identity. Adopt only on a measured replay/history saving that repays a second codec.

It also cites Goose's inferred (annotation-free) safety as a data point for the vision's generability question. Docs only: no dependency, no claim from Goose's benchmarks.

Checks: bun run docs:check, bun run build:site.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
algal	Ready	Preview	Oct 8, 2026 6:26am UTC

[0thernet]

This has had red CI and no commits since 10-08, and yesterday's ask on #278 to fix or close it went unanswered. Decide today: push a fix that turns CI green, or close it. If the Goose reference still matters, put it in one paragraph in the north star's references in a later PR. It shouldn't sit open as a red PR.