Checking registry…

Codifide Public Registry

Content-addressed symbols, served by hash. Any agent on any machine resolves the same identity to the same bytes — guaranteed by SHA-256, not by trust.

3 published symbols
SHA-256 content addressing
CDN global edge delivery

How it works

A symbol's identity is the SHA-256 of its canonical CBOR bytes. Two agents naming the same hash see the same code — the same intent, the same effects, the same contracts. No version numbers. No drift.

1

Write a Codifide function

Every function declares its intent, effects, and contracts. The canonical form is deterministic — the same function always produces the same hash.

2

Publish by hash

Push to the registry with codifide store push sha256:<hash>. The registry stores the canonical CBOR and serves it from the global CDN.

3

Import from anywhere

Any agent resolves the symbol with import f = sha256:<hash> and --registry https://codifide.com. Hash-verified on every fetch.

Published symbols

The canonical content-moderation pipeline — the reference implementation used in all four agent case studies. Import any symbol by its hash.

classify_content ( message: String ) → Label
effects {}

"classify a message as safe, unsafe, or uncertain based on keyword signals"

sha256:377099c5bddb8cebe9e8bc6b8499bb00ea99083798d1b064799ac82c55636fae
moderate ( message: String ) → Label
effects {} believe

"gate classification on confidence — refuse when confidence is too low"

sha256:1bbe69ba7dae84a1fc1a5b335ac2fd9f4be3e4462857db3cc0d38c4af5be4a2a
route_message ( message: String ) → String
effects {} believe

"route a message to blocked, approved, escalate-to-human, or refuse"

sha256:68c15e1108ac195e211634d2755f58353422db61b077690ec59686ad87d2d964

Try it live

Run the composed pipeline against the public registry from your machine:

# pipeline_composed.cod imports all three symbols by hash
python3 -m codifide run pipeline_composed.cod \
  --registry https://codifide.com

# Output: blocked
# (classify_content, moderate, and route_message
#  all resolved from the public registry)

Publish your own symbols

Any Codifide function can be published to the registry. Once published, any agent anywhere can import it by hash — no out-of-band coordination, no version negotiation, no trust required beyond the hash itself.

1
Store locally python3 -m codifide store put my_module.cod
2
Push to the registry python3 -m codifide store push sha256:<hash> --registry https://codifide.com
3
Share the hash import my_fn = sha256:<hash>
Hash-verified on every fetch

The registry cannot serve a different symbol under the same identity. Every fetch verifies the SHA-256 hash before the bytes are used. Tampering changes the hash — and the hash is the identity.

API reference

The registry speaks the Codifide RPC API. All endpoints return canonical CBOR by default, JSON on request.

Endpoint Method Description
/health GET Liveness check. Returns {"status":"ok"}.
/symbols/<hash> GET Retrieve a symbol by SHA-256 identity. Add Accept: application/json for JSON.
/symbols/<hash> HEAD Existence check. 200 if present, 404 if not.
/symbols/<hash>/imports GET Resolve the direct imports of a stored symbol.
/symbols POST Publish a symbol. Requires Authorization: Bearer <token>. Body: canonical CBOR or JSON.