Skip to content

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

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) #105

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 @@ -70,7 +70,7 @@ The following files in `.machine_readable/` contain structured project metadata:
does not carry an `adapter/` directory of its own. Its front doors (MCP
stdio/TCP, HTTP intake) are Elixir/OTP by architecture decision, unrelated
to the Zig adapter pattern.
- Naming lineage: the fuller "Hexadeca-Connector" (16-protocol-surface) pattern
- Naming lineage: the fuller "UnifiedApiAdapter" (16-protocol-surface) pattern
lives in `hyperpolymath/hypatia` and `hyperpolymath/proven-servers`, descended
from a **retired** V-lang reference (`developer-ecosystem/v-ecosystem/v_api_interfaces`),
replaced by Zig+Idris2+Rust-client per the estate-wide V-lang ban
Expand Down
Loading