GPS ·
GPS · General index · Catalogue no. 0001

Gross
Poetry
Systems


Control surfaces for uncertain machines. A small, opinionated catalogue of open-source tools for agent-era work. Tools building tools: each is its own object, and each is built and maintained with the others.

01 · The catalogue / in print

GPS-0002 · Docs

Poolboy

Maintain software documentation as portable Markdown, then compile it into a static corpus agents can query.

npm install --global @grosspoetrysystems/poolboy
v0.3.0 · GPL-3.0 · source
GPS-0003 · Governance

Helicopter

Intake for human, AI-assisted, and agent-authored contributions: PR contracts, trusted-base checks, a turn queue, and a human who merges.

npx skills add grosspoetrysystems/helicopter
v0.2.0 · MIT · source
GPS-0004 · Workspace

Vernacular

A private working space beside every repository, so durable agent work never pollutes a commit.

npm install --global @grosspoetrysystems/vernacular
v0.3.0 · MIT · source
GPS-0005 · Profiles

OOMPF

Share, inspect, and install reproducible OMP agent profiles. Your YAML stays in your Gist.

npm install --global @grosspoetrysystems/oompf
v0.4.1 · MIT · oompf.run · source
GPS-0006 · Readiness

Crooked Pattern

A deterministic, evidence-backed score for how ready a repository or website is for agents.

npx @grosspoetrysystems/crooked-pattern scan --url https://your-site.com
v0.1.2 · MIT · source

02 · In the works / not yet in print

Pending · Memory

Sea Noise

A personal cognition layer on a Markdown vault. Local-first, audience of one, a mirror rather than an assistant.

Pending · Secrets

Dummy

Secrets by indirection: pointers in your .env, plaintext only at the point of use, paired with a governed execution sandbox.

Pending · Harness

Steel Cars

A composable single-agent runtime. Unpainted on purpose.

§ About / notes on practice

  • Local-first, human-first. The individual is primary.
  • Choose the most durable tool, language, or pattern for the job. Minimize dependencies.
  • Publish into the ecosystems where the audience and collaborators already are.
  • Shared orchestration, not shared visibility.
  • Governance is part of UX, not a layer above it.
  • Ship the canonical implementation. Adoption is by example.
  • Subtract until restraint shows. Features that don’t earn their keep are removed, not deferred.

§ Contact

Write to us →