gooo-go-ports

Gooo Go Ports

Gooo is an experimental language for describing program behavior and retaining how a program was built and run. This repository provides independently checked Go ports and original Gooo compositions. Start with one source change and an observable result.

First task for a coding agent

Open this checkout in Codex, Cursor or Claude Code and ask:

Follow .agents/skills/gooo-first-program/SKILL.md. Run the Gooo example, change its score threshold from 60 to 80, then save and replay a new execution. Show the actual changed result and keep my existing files.

With the supplied inputs, score 75 changes from sensor: high to sensor: low; its other three returned fields stay unchanged. The first-program skill and setup guide target Go 1.27.3 on macOS or Linux with the compiler identity pinned by the checkout. Reuse tools only after identity validation; source setup may download and build them. The full main CI at b0e6715 passed with Go 1.27.3 and the pinned compiler, including native comparison and saved replay. Older immutable bundles and walkthroughs retain the toolchain identities recorded in their own release instructions. A source edit needs native execution. Saving generated Go alone is not a run. For an existing Tessl setup, use the project-local source installation to give the same first-program task to your coding agent.

Gemini CLI users can load the same instructions through the optional context extension.

If setup or execution fails, report the first failed step and diagnostic. An incomplete attempt is useful feedback. Share public source and inputs only.

Choose the next useful task

These examples calculate bounded facts and policy decisions. Live effects still need current host-owned authority and atomic application. Input-only OBSERVED records describe finite runs; they are not expected-output verification or a proof for all inputs. Tell us the real API or automation task you want to solve in the feedback form.

The language engine owns Gooo syntax and compiler development. This ecosystem repository owns the ports, examples and their independent Go references.

More workflows, supported domains and verification history

Use Gooo with a coding agent: follow the first-program skill to edit actual Gooo source, execute it and save a replay. The agent setup guide covers repository discovery in Codex and Cursor, explicit use in Claude Code, and the limits of the existing policy examples.

Install the policy comparison command: run the immutable CLI without cloning. It compares the same nine supplied facts under two fixed profiles and rechecks saved reports; this immutable installation recipe retains its Go 1.27.2 profile.

Compare API policy decisions in CI: run the existing policy review, whose Action pins module revision e723f9af6dc3 and compares nine supplied facts using the fixed original and cel-api-readonly-v1 profiles. In that pinned revision, an otherwise allowed write changes from ALLOW to ACTION_NOT_READ_ONLY, while an allowed read stays unchanged; optionally fail CI on NEWLY_DENIED. The current cel-api-readonly-principal-v1 profile preserves original base denials and also requires principal_present == true and a nonempty raw principal_value for an otherwise allowed read. For that otherwise allowed read, a false presence flag or empty raw value returns EXPLICIT_PRINCIPAL_REQUIRED; a whitespace-only raw value is nonempty because whitespace is not trimmed. These profiles cannot load arbitrary policies, and comparison results do not authorize live API actions.

Try service-policy checks from Go: open the four-file service-policy quickstart. For this frozen Go 1.27.2 example, follow its README to run Go generated from Gooo without a runtime Gooo compiler. Distinguish invalid input from denial, compare the same request before and after a rule change, and inspect a returned widening witness. These calls compare supplied policy facts; they do not apply a grant or call a service.

Try a Gooo path diagnostic: compare two path spellings, keep both originals, and see whether slash cleaning makes them equal. Run the supplied inputs, inspect three results and save a replay; these lexical facts do not grant access or establish router/filesystem identity.

Try automatic header diagnostics: inspect a header name and value, strictly decode external JSON, then retain both strings and the first invalid byte in a twelve-field Gooo report. No per-request human approval is needed to calculate the facts.

Compose an automatic header-addition decision: the diagnostic-header addition combines header facts, payload admission and twelve supplied request observations. Inspect sixteen fields, preserve the candidate and byte witnesses, then use a fresh Gooo-generated local host for an atomic revision check and application.