# Sandwich Hime > **Canonical project:** development, contribution and security instructions, > releases, and stewardship live on the > [founder-controlled Gamertan Gitea](https://gitea.speelman.ca/gamertan/sandwich-hime). > A GitHub copy, when present, is a read-only discovery snapshot rather than a > contribution or release authority. Sandwich Hime is an HTML-first, ahead-of-time template engine for Go. Hime-san keeps the direct, mixed-markup feeling of classic PHP while compiling trusted `.sando` templates into typed, deterministic Go components that an ordinary `go build` can audit and deploy. ```sando

``` The generated API is ordinary Go: ```go func Profile(page ProfileView) sando.Component ``` Templates are what authors write. Components are the typed output and composition unit. Hime-san is an intentionally opinionated development tool, not an application framework: a consuming project keeps its `.sando` sources, commits the adjacent `.sando.go` output, and imports only the small Apache-2.0 `sando` runtime. Hime-san never owns the router, middleware, layout policy, request object, or production server. ## Status `v1.0.0-beta.2` is the current compiler beta. It is supported for learning, classroom projects, evaluation, and compatibility feedback. It is a semantic-version prerelease: source syntax, generated output, the runtime API, and CLI behavior may change before final v1, and this beta is not recommended for production deployment. The exact Beta 1 source passed maintainer-run native Windows and executed Linux matrices with Go 1.25.12 and Go 1.26.5. Native macOS validation is still pending, so macOS support is provisional in this beta. Mac learners and Go developers are warmly invited to try it and share their macOS version, architecture, Go version, command, and smallest useful reproduction. Community reports broaden the evidence; maintainers remain responsible for security review, triage, fixes, and release decisions. Inside an application module, add the small runtime first: ```sh go get gamertan.com/sandwich-hime/sando@v1.0.0-beta.1 ``` Then install the current beta compiler: ```sh go install gamertan.com/sandwich-hime/cmd/himesan@v1.0.0-beta.2 ``` Keep that runtime-first order. It avoids path-selection ambiguity between the parent compiler module and its independently tagged nested runtime. If the compiler was installed first and `go get` reports that the parent module does not contain `sando`, seed the exact nested module without clearing the global cache, then retry: ```sh go mod download gamertan.com/sandwich-hime/sando@v1.0.0-beta.1 go get gamertan.com/sandwich-hime/sando@v1.0.0-beta.1 ``` For a reproducible one-off or classroom invocation that does not depend on the learner's `PATH`: ```sh go run gamertan.com/sandwich-hime/cmd/himesan@v1.0.0-beta.2 --help ``` The unchanged runtime remains `sando/v1.0.0-beta.1`; compiler versions are independent. Beta 2 adds `himesan lsp --stdio` without changing the runtime ABI. Signed compiler tags, direct fetching, the public Go proxy, and the checksum database are verified after publication. A newly announced version may still need a short propagation interval before every proxy sees its immutable tag. For repository development: ```sh go install ./cmd/himesan ./scripts/verify.sh ./scripts/check-licenses.sh ``` The portable path is `generate`, `check`, and the project's normal Go tools. For people who want the paved road, `himesan dev` deliberately does more: it builds the application's own `net/http` program in the user cache, health-checks a random loopback candidate, preserves the last healthy process, and serves it through `http://127.0.0.1:7331` with local-only reload diagnostics. That is a Cole-shaped convenience, not a production server or a requirement. Take the paved path—or don't. Beta 2 also provides a standard, editor-neutral language server. It analyzes unsaved overlays with the compiler's real parser and context model, but never generates, runs Go, executes a project, fetches a module, accesses the network, or starts the dev supervisor. See [the language-server contract](docs/LANGUAGE_SERVER.md). The portable Agent Skill and VS Code preview live in the separate [tooling repository](https://gitea.speelman.ca/gamertan/sandwich-hime-tooling). Final-v1 installs will use the same paths with `@v1.0.0`. A version is advertised as available only after its immutable tags, `gamertan.com` metadata, and clean direct-fetch installation have been verified. ## The contract - One typed template, compiled into one component constructor, per `.sando` file. - Go statements are trusted source code; rendered values are untrusted. - `` escapes for the statically known HTML context. - `` composes another component and propagates errors. - Ambiguous or unsupported HTML contexts fail compilation. - Generation is deterministic and formatted; each owned output is replaced atomically, and handwritten Go and `go.mod` are never edited. - `check` is read-only and detects invalid or stale generated output. - Production builds need no compiler binary. The language is specified in [SPEC.md](SPEC.md). The security boundary is in [docs/THREAT_MODEL.md](docs/THREAT_MODEL.md), the development loop is in [docs/DEVELOPMENT_SERVER.md](docs/DEVELOPMENT_SERVER.md), and the multi-license boundary is in [LICENSES.md](LICENSES.md). User-authored templates and generated application files remain under terms chosen by their authors to the extent they hold the necessary rights. The compiler is AGPL-3.0-only, the runtime is Apache-2.0, and [OUTPUT_EXCEPTION.md](OUTPUT_EXCEPTION.md) grants an additional permission for Cole Speelman-owned generator scaffolding copied into output. ## Names matter - Project: **Sandwich Hime / Hime-san** - CLI: `himesan` - Template: `page.sando` - Generated Go: `page.sando.go` - Runtime: `sando` - `.san`: reserved exclusively for the separate San language The project is never marketed as bare “Hime”; that name is already used by an unrelated Go web framework. ## Why This is a love letter to hand-built web development: the immediacy of Cole's 2004 Geocities page for a PSO Gameclub, with typed interfaces, reproducible builds, modern contextual safety, and boring production operations. The first prototype was a wonderfully cursed princess that could `bless` or `rebuke` templates, announced when Hime-san was resting, and concluded that creating a compiler was not hubris but destiny. The jokes stayed because developer joy is part of the point. The security boundary grew up because care is part of the point too. Cole builds with ADHD, neurodivergence, a disabled body, finite energy, and a family he wants to leave understandable work for. Clear files, calm defaults, accessible documentation, last-good development builds, and honest limitations are therefore operating requirements—not decorative empathy. The project aims to leave room for individuals, tiny teams, learners, disabled people, and anyone too small to win a complexity contest. Open source permits corporate use. Independence comes instead from the AGPL-3.0-only compiler, the Apache-2.0 runtime, application-owned generated output, contributor-held copyright, founder-led governance, release-key control, and careful trademark stewardship. Companies may use and contribute; participation does not confer ownership of the identity or project. The fuller origin, Japanese craft inspirations, family dedication, human-art commitment, and stewardship boundary live on the [project site](https://sandwichhime.com/docs/project/). The official [step-by-step lesson](https://sandwichhime.com/docs/tutorial/) lives with that documentation, and its [0BSD runnable companion](https://gitea.speelman.ca/gamertan/sandwich-hime-tutorial) has a separate repository and history. Tutorials and copyable applications are maintained separately from this compiler repository. Performance claims will follow repository-owned measurements, never precede them.