Files
zeekay f73044869d nine more modules answer at their own address
The set was 66 while cloud depends on 75 of our Go modules. The nine missing
ones are the provable cases: each is a row in cloud's manifest.Apps, so it is
ours by construction rather than by reading a name. amqp, flags, framework and
licensing have no page and get one; account, captable, dataroom, pricing and
zen already had a product page, so the tag joins the metadata that page already
declares — measured after, all five keep their own titles.

Left out on purpose: the vendored forks cloud also depends on — decimal,
govaluate, goauthorizenet, go-openai-realtime, go-cosyvoice, krakend-otel.
Serving hanzo.ai/decimal for a fork of somebody else's library would claim a
name we did not earn.

Verified against a real dev server rather than the markup: all nine answer
?go-get=1 with their tag, and iam still does too.
2026-08-22 00:11:03 -07:00

16 lines
655 B
TypeScript

import CaptableClient from "./captable-client"
import { goImport } from '@/lib/go-modules'
// This path is a product page AND the import path of a Go module. The tag is
// invisible to a reader and is the whole of what the go tool reads; it joins
// this page's metadata rather than replacing it. Defined once in lib/go-modules.
export const metadata = {
other: goImport('captable'),
title: "Hanzo Cap Table - Equity Management Platform",
description: "Manage share classes, stock options, SAFEs, convertible notes, and equity plans. The open-source alternative to Carta.",
}
export default function CaptablePage() {
return <CaptableClient />
}