Files
skills/public/hip-1193.md
zeekayandHanzo Dev 807ff47973 cloud-host: the local cloud, written down
An outside adopter built a product on this stack in a day and lost most of
their time to one gap: nothing documents how to run the cloud locally. They
wrote four launcher scripts, each minting a master key by hand, and shipped
every service unauthenticated on loopback to reach where one existing command
already gets you.

That command is `hanzo host serve`. It binds a unix socket rather than a port,
and loopback where it binds one at all — safer than what they built to replace
it, and mentioned in no README. `hanzo up` is the heavier path: k3s in a
microVM with the cloud deployed into it, for when the cluster shape is what you
are testing.

The page states the port that actually matters. 3690 is what `local` means to
`hanzo network`; the 8080 in the cloud README is the container's, and a URL
built from one while the other runs is a connection to nothing. Their commit
history contains exactly that fix.

It also says what does not work locally, rather than leaving it to be found one
command at a time: KMS needs an IAM principal and there is no IAM on a laptop,
so the in-process client that skips the guard makes local a different code path
from deployed. And it records the at-rest encryption report as unreproduced,
because it is — a boot log claiming encryption is not evidence, and the page
says to read the file header instead.

A "do not rebuild these" table names the six things they wrote from scratch
because they could not find ours, and admits the one that genuinely does not
exist: a single-box self-host guide.

Their two practices worth copying are in here too — a positive control on any
exposure test, and recording what was executed separately from what was only
written.

The manifest gains a self-hosted section, so an agent pasted the URL learns what
differs locally before it discovers it the hard way.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-10 22:45:05 -07:00

2.6 KiB

hip, title, author, type, category, capability, status, implementation-go, created, requires
hip title author type category capability status implementation-go created requires
1193 Standing — Entity Upkeep and Annual Filings Hanzo AI Standards Track Application standing Final shipped 2026-09-10 HIP-0026, HIP-0106, HIP-0139

HIP-1193: Standing — Entity Upkeep and Annual Filings

Abstract

/v1/standing is the canonical capability for standing within the Hanzo Cloud platform. Package standing prices and tracks what it costs to KEEP a company, as distinct from what it cost to form one. The implementation is hanzoai/cloud apps/standing and plugin/standing (HIP-0106, HIP-0139). All operations are native, composable, and authenticated against Hanzo IAM (HIP-0026).

Motivation

Before this specification, standing operations lacked a unified canonical surface or were scattered across disparate endpoints. Under HIP-0139 (§1), every cloud capability maps 1:1 with exactly one plugin binary, one address prefix, one client class, and one authoritative specification. This eliminates duplicate implementations and ensures strict physical isolation, predictable billing, and orthogonal composability across the estate.

Specification

The key words MUST, MUST NOT, and SHOULD are to be interpreted as in RFC 2119.

§1 Addresses and Operations

The standing capability answers exclusively under its assigned route prefixes:

Method Path Summary
POST /v1/standing/upkeep Reports what keeping this entity costs every year, itemised.

§2 Storage and Physical Isolation

Data is isolated physically per organization using cloud.OrgDB: {DataDir}/orgs/{org}/standing.db. Isolation is strictly enforced at the filesystem and OS level; no cross-tenant queries are permitted. Where temporal or timeseries data is captured, postings are signed and immutably appended.

§3 Authentication and Principal

Every request reaching /v1/standing MUST present a valid Hanzo IAM bearer token (HIP-0026, HIP-0111). Anonymous requests are rejected at the edge gateway before invoking the plugin. The executing principal is extracted from the token and bound to the request context.

Security Considerations

  1. Physical Separation: Each tenant retains an isolated SQLite database file.
  2. Replay & Channel Binding: Direct dials and internal RPCs enforce channel binding over ZAP native transport.
  3. Audit Trails: All state-modifying actions emit immutable audit events to the centralized event plane (HIP-1190).

References

  • HIP-0026: Identity & Access Management Standard
  • HIP-0106: Hanzo Plugin Contract
  • HIP-0139: Capability Standard