Files
skills/public/hip-0142.html
zeekayandHanzo Dev 9e10c1c10e Each llms index points at the other two
hanzoskills.com/llms.txt now opens with the install line, the API
reference index and the company index, so an agent that lands on any
one of the three can find the rest.

robots.txt claimed 537 documents while llms.txt counts 920. The number
is gone from robots.txt; llms.txt derives it.

public/ is regenerated from scripts/site.py, which it had fallen
behind: the copy-prompt menu and agent bar were in the generator and
not in the committed pages. tests/site.mjs passes against the result.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-11 00:27:59 -07:00

270 lines
24 KiB
HTML

<!doctype html>
<html lang="en"><head>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>hip-0142</title>
<meta name="color-scheme" content="dark">
<style>
/* Committed to one visual world: a dark instrument panel. No light variant —
the dot field and the hairline rules only read on black, and a naive
inversion would wash both out. Every colour is painted explicitly so the page
never borrows a host background. */
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
:root{
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
--font-zen-pixel-square:'Zen Pixel Square',monospace;
--mono:var(--font-zen-mono);
--sans:var(--font-zen-sans);
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
--r:999px; --r-soft:14px;
}
*{box-sizing:border-box}
html{-webkit-text-size-adjust:100%}
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
/* The dot field. A halftone made of one repeating radial-gradient, faded out
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
/* No overflow clip here: the dot field is inset to the box already, and a clip
would cut off the copy-prompt menu. */
.hero{position:relative;border-bottom:1px solid var(--line)}
.hero::before{content:"";position:absolute;inset:0;
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
background-size:7px 7px;
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
pointer-events:none}
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
nav{border-bottom:1px solid var(--line)}
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
justify-content:space-between;align-items:center;gap:1rem}
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--ink);text-decoration:none;
display:inline-flex;align-items:center;gap:.6rem}
.brand i{font-style:normal;color:var(--faint)}
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--soft);text-decoration:none}
nav a.up:hover{color:var(--ink)}
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
h1 em{font-style:normal;color:var(--faint)}
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
line-height:1.2;font-weight:400}
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
.btn.solid:hover{background:#d8d8d4}
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
/* Copy-prompt selector. Each row copies the prompt for its own target. */
.copy{position:relative;display:inline-flex}
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
padding:.4rem;display:flex;flex-direction:column;
box-shadow:0 12px 32px rgba(0,0,0,.75)}
.menu[hidden]{display:none}
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
white-space:nowrap}
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
.mi:hover .mark{color:var(--ink)}
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
letter-spacing:.1em;text-transform:uppercase}
/* Works-with bar: one scrolling row, name and mark per agent. */
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
display:flex;align-items:center}
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
-webkit-overflow-scrolling:touch;
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
.bar::-webkit-scrollbar{display:none}
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
text-decoration:none;background:var(--ground)}
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
.agent .mark{width:.95rem;height:.95rem}
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
p{margin:0 0 1rem;max-width:70ch}
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
li{margin:.22rem 0}
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
text-decoration-color:var(--line-hi)}
a:hover{text-decoration-color:var(--ink)}
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
display:block;overflow-x:auto}
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
.curl{display:block;background:var(--panel);border:1px solid var(--line);
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
white-space:pre;line-height:1.9}
.curl b{color:var(--ink);font-weight:400}
.curl i{font-style:normal;color:var(--faint)}
/* index */
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
#q:focus{outline:none;border-color:var(--soft)}
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
text-transform:uppercase;margin:0 0 2rem}
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
padding-bottom:.45rem}
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
border-radius:var(--r-soft);text-decoration:none}
.row:hover{background:#0a0a0a}
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
color:var(--faint);font-size:.85rem}
footer a{color:var(--soft)}
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
margin:0 0 2rem;font-size:.85rem}
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
border-bottom:1px solid var(--line);padding-bottom:.4rem}
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
.fmap a:hover{text-decoration:underline}
.fmap div{color:var(--faint);line-height:1.5}
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
@media (max-width:640px){
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
.btns{gap:.5rem}
.btn{padding:.75rem 1.15rem;font-size:.68rem}
.copy,.copy .btn{width:100%;justify-content:center}
.menu{left:0;right:0;min-width:0}
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
.strip b{border-right:0;padding-right:0}
.bar{width:100%}
}
</style>
<link rel="alternate" type="text/markdown" href="/hip-0142.md">
<link rel="icon" href="/favicon.svg">
<link rel="canonical" href="https://hanzoskills.com/hip-0142">
</head>
<!-- Reading this with a machine? Every page here is also plain markdown.
This one: https://hanzoskills.com/hip-0142.md
Index: https://hanzoskills.com/llms.txt
Corpus: https://hanzoskills.com/all.md
Append .md to any path for the markdown twin. -->
<body>
<nav><div class="in">
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
<a class="up" href="/">All skills</a>
</div></nav>
<div class="wrap">
<h1>hip-0142</h1><p class="lede">HIP-142: One Manifest, Five Kinds. Status Draft. Hanzo architectural specification.</p><h1>HIP-0142: One Manifest, Five Kinds</h1>
<h2>Abstract</h2>
<p><code>hanzo.yml</code> is the one file a repository uses to declare itself to the build fabric. It is <strong>data</strong>. Many readers can read data; only a runtime can execute code — so there is no <code>hanzo.ts</code>, no <code>hanzo.go</code>, no <code>hanzo.rs</code>. Any language may <em>generate</em> <code>hanzo.yml</code> as a dev-time step, and exactly one thing is the contract.</p>
<p>Today the manifest says what to <strong>test</strong> and what <strong>image</strong> to build. It cannot say what the project <em>is</em>. A repository that ships a Helm chart, a <code>compose.yml</code>, a function with no Dockerfile, or a whole release of charts has no field to say so, so each of those arrives by an arrangement outside the file.</p>
<p>This HIP adds one field — <code>kind</code> — and one optional companion — <code>path</code>. <code>kind</code> names how a project arrives; each value maps to exactly one runtime primitive. <code>kind</code> absent means what the file means today, so every manifest in the fleet keeps working unedited.</p>
<h2>Motivation</h2>
<p>Measured over the <code>hanzo</code>, <code>lux</code> and <code>zoo</code> checkouts:</p>
<pre><code>find ~/work/{hanzo,lux,zoo} -maxdepth 2 -name hanzo.yml | wc -l # 103</code></pre>
<p>Every top-level key that actually appears in those 103 files, and how many declare it:</p>
<p>| key | files | read by | |---|---:|---| | <code>test</code> | 90 | ci | | <code>images</code> | 36 | ci, platform, the push reactor | | <code>kms</code> | 9 | ci, platform | | <code>version</code> | 5 | ci | | <code>site</code> | 2 | ci | | <code>deploy</code> | 2 | ci, platform | | <code>client</code> | 2 | ci | | <code>e2e</code> | 1 | platform | | <code>build</code> | 1 | platform |</p>
<p>Two further keys are read and declared by no repository in that survey — <code>binaries</code> and <code>bucket</code>, the artifact lane read by ci and by <code>hanzo build</code> — and two more are read by platform alone: <code>publish</code> and <code>source</code>.</p>
<p>The number that matters is this one: <strong>66 of the 103 declare no image lane at all.</strong> They are not broken. Most are test gates, and platform&#x27;s validator returns &quot;nothing here for me&quot; for them on purpose. But that same silence is what a chart repository produces, and a chart repository <em>does</em> have something to deliver. One absence is being asked to carry two opposite meanings, and no reader downstream can recover which was intended.</p>
<h2>Specification</h2>
<p>The key words MUST, MUST NOT, SHOULD, SHOULD NOT and MAY are to be interpreted as in RFC 2119.</p>
<h3>1. <code>kind</code> — one field, five values</h3>
<pre><code class="lang-yaml">kind: image | fn | chart | compose | universe</code></pre>
<p><code>kind</code> names how the project arrives at the fabric. It is optional, and <strong>absent means <code>image</code></strong>, which is what every manifest in the fleet already means.</p>
<p>A reader that does not recognise the value MUST refuse the manifest rather than guess at it. The set is closed: a sixth arrival is a new HIP, not a new string.</p>
<h3>2. <code>path</code> — where that kind reads from</h3>
<pre><code class="lang-yaml">path: &lt;repo-relative path&gt;</code></pre>
<p>Optional, one per manifest, with a default per kind:</p>
<p>| kind | default <code>path</code> | what it points at | |---|---|---| | <code>image</code> | — | unused; each <code>images:</code> entry carries its own <code>context</code> | | <code>fn</code> | <code>.</code> | the build context | | <code>chart</code> | <code>chart</code> | a chart directory | | <code>compose</code> | <code>compose.yml</code> | a compose file | | <code>universe</code> | <code>charts</code> | a directory of chart directories |</p>
<p><code>path</code> MUST be repo-relative and MUST NOT ascend. <code>..</code> and absolute paths are refused, along with any character outside <code>[A-Za-z0-9._/-]</code>, by the same rule and for the same reason as <code>kms.path</code> (HIP-0136 §1): the value reaches a clone as a path segment, and a value that can traverse upward re-addresses the read.</p>
<h3>3. Each kind is exactly one runtime primitive</h3>
<p>| kind | build | release | |---|---|---| | <code>image</code> | BuildKit, <code>dockerfile.v0</code> frontend, the repo&#x27;s Dockerfile | operator workload CR — <code>deploy.target.crd</code>, default <code>App</code> | | <code>fn</code> | the same door with <strong>no Dockerfile</strong>: <code>hanzoai/pack</code> is the gateway frontend and detects the ecosystem | operator <code>Function</code> CR, invoked at <code>/v1/functions/{name}/invoke</code> | | <code>chart</code> | nothing | one <code>HelmChart</code> — chart bytes and values, both from <code>path</code> | | <code>compose</code> | nothing | the compose file at <code>path</code>, converted to that same <code>HelmChart</code> | | <code>universe</code> | nothing | every chart under <code>path</code>, one release |</p>
<p>Two properties hold this together. <code>compose</code> is not a second delivery mechanism but a <em>notation</em> that converts to the chart primitive, so nothing downstream of the conversion can tell the difference. And <code>fn</code> differs from <code>image</code> only in which BuildKit frontend runs and which CR receives the result — one build door serves both, and <code>fn</code> MUST NOT add a second.</p>
<h3>4. <code>kind</code> is not <code>deploy.target.crd</code></h3>
<p>Two fields spell a Kubernetes-shaped noun and they sit on different axes.</p>
<ul><li><code>kind</code> names <strong>what the repository is</strong>, before anything is built.</li><li><code>deploy.target.crd</code> names <strong>which operator CR a built image rolls onto</strong> —</li></ul>
<p> <code>App</code> or <code>Service</code> — and is meaningful only for <code>kind: image</code>.</p>
<p>Conflating them would make <code>kind: chart</code> ask for a workload CR carrying an image the chart lane never builds.</p>
<h3>5. Compatibility</h3>
<p><code>kind</code> absent is <code>image</code>, and <code>image</code> is today&#x27;s behaviour to the letter:</p>
<ul><li><code>images:</code> present → build them (unchanged).</li><li><code>build:</code> present → build it (unchanged).</li><li>neither, and no <code>deploy:</code> → the manifest declares nothing for the build lane</li></ul>
<p> (unchanged: platform&#x27;s validator answers null, ci runs the <code>test:</code> gate).</p>
<ul><li>neither, with <code>deploy:</code> → still an error (unchanged).</li></ul>
<p>A manifest naming <code>kind: chart</code>, <code>compose</code> or <code>universe</code> declares <strong>no</strong> image lane, and <code>images:</code>/<code>build:</code> are meaningless in it. A reader MUST NOT answer &quot;nothing here&quot; for such a manifest. That confusion is what this HIP removes.</p>
<h3>6. Readers</h3>
<p><code>hanzo.yml</code> has four readers, and each must be taught <code>kind</code> on its own. Until it is, a reader treats every manifest as <code>kind: image</code> — correct for the whole fleet today, and wrong the moment a chart repository declares itself.</p>
<p>| reader | entry point | reads | what <code>kind</code> changes there | |---|---|---|---| | <code>hanzoai/ci</code> | <code>.hanzo/workflows/build.yml</code> — the <code>yq</code> expressions in <code>Test (per hanzo.yml)</code>, <code>KMS login</code>, <code>Build &amp; push images</code>, <code>Build &amp; publish binaries</code>, and the client and site steps | <code>test</code>, <code>images</code>, <code>kms</code>, <code>version</code>, <code>site</code>/<code>sites</code>, <code>client</code>, <code>binaries</code>, <code>bucket</code> | skip the image lane for <code>chart</code>/<code>compose</code>/<code>universe</code>; swap the frontend for <code>fn</code> | | platform | <code>hanzoai/platform</code>, <code>pkg/platform/src/services/ci/platform-config.ts</code> — <code>validatePlatformConfig</code> | <code>images</code>, <code>build</code>, <code>deploy</code>, <code>e2e</code>, <code>publish</code>, <code>kms</code>, <code>source</code> | the schema and the validator, where <code>kind</code> is defined. Then <code>build-scheduler.ts</code> (schedules nothing for a chart kind, correctly, and releases nothing either), <code>buildkit-job.ts</code> (<code>--frontend=dockerfile.v0</code> → the pack gateway for <code>fn</code>), <code>build-completion.ts</code> (the chart release), <code>k8s/operator/cr-builder.ts</code> (a <code>HelmChart</code> is not one of <code>WORKLOAD_KINDS</code>) | | <code>hanzo build</code> | <code>hanzoai/cloud</code>, <code>cli/commands.go</code> — <code>(*BuildReq).loadRecipe</code> | <code>binaries</code>, <code>bucket</code> | refuse a chart repository by name, rather than by &quot;declares no binaries:&quot; | | the push reactor | <code>hanzoai/cloud</code>, <code>apps/git/build_on_push.go</code> — <code>readPipeline</code>, <code>pipelineFromBlob</code>, the <code>pipeline</code> struct | <code>images</code> | a <code>kind: chart</code> push MUST NOT be a silent no-op |</p>
<p>The build door itself — <code>hanzoai/cloud</code>, <code>apps/platform/runner.go</code> — reads no <code>hanzo.yml</code>. The recipe reaches it verbatim in the request body, so it grows a chart lane only when a caller sends one.</p>
<h2>Rationale</h2>
<p>The obvious alternative is to keep inferring: a repository with a <code>Chart.yaml</code> is a chart, one with a <code>compose.yml</code> is a compose project, one with neither is a test gate. Inference costs nothing to adopt and cannot be made correct. A repository may hold a chart <em>and</em> a Dockerfile — most of ours that hold a chart do — so the files present do not order themselves, and every reader would need the same precedence table, written four times, drifting from the day it lands.</p>
<p>The second alternative is a per-kind block: <code>chart: { path: … }</code>, <code>compose: { file: … }</code>. It carries the same information as <code>kind</code> plus <code>path</code> and reintroduces the ambiguity, because two blocks can be present at once.</p>
<p>One scalar naming the arrival, and one scalar saying where it reads from, is the smallest thing that is unambiguous by construction.</p>
<h2>Security Considerations</h2>
<p><code>path</code> is attacker-influenced in the sense that matters: it is committed by whoever can push to the repository, and it is consumed as a path segment against a checkout and, for the chart kinds, against the directory whose bytes become a release. An unchecked value reads outside the repository. §2 therefore fixes the charset and refuses <code>..</code> at parse time rather than at each use site, which is the same boundary discipline <code>kms.path</code> uses and for the same reason: validating once where the value enters keeps every consumer safe without every consumer knowing.</p>
<p><code>kind</code> itself grants nothing. It selects among primitives a caller could already reach, and a value outside the closed set is refused rather than defaulted, so it cannot be used to steer a manifest into an unintended lane.</p>
<h2>References</h2>
<ul><li>HIP-0014 — Application Deployment Standard</li><li>HIP-0036 — CI/CD Build System Standard</li><li>HIP-0136 — One Secret, One Path</li></ul>
<h2>Copyright</h2>
<p>Released under CC0 1.0 Universal Public Domain Dedication.</p>
<footer>
<div class="fmap">
<div><b>Build</b>
<a href="https://hanzo.app">hanzo.app</a> app builder
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
<div><b>Run</b>
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
<div><b>Account</b>
<a href="https://hanzo.id">hanzo.id</a> sign in
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
<div><b>Company</b>
<a href="https://hanzo.ai">hanzo.ai</a> canonical
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
</div>
<div class="fend"><a href="/hip-0142.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
</footer>
</div></body></html>