Skip to content

refactor: rename Hexadeca → unified-api-adapter (estate-wide) #332

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hyperpolymath merged 1 commit into from
Sep 21, 2026
Merged

refactor: rename Hexadeca → unified-api-adapter (estate-wide) #332

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude/CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ contract when it has one) before a single dispatch call into the one Zig ABI
unified Zig core; adapters bind loopback and sit behind it.

Naming lineage: the fuller 16-protocol-surface pattern is called the
**Hexadeca-Connector** elsewhere in the estate (`hyperpolymath/hypatia`,
**UnifiedApiAdapter** elsewhere in the estate (`hyperpolymath/hypatia`,
`hyperpolymath/proven-servers`) — same Idris2-ABI + Zig-FFI substrate, more
protocol surfaces. It descends from a now-**retired** V-lang reference
(`developer-ecosystem/v-ecosystem/v_api_interfaces/v_api_interfaces.v`),
Expand Down
Loading