haiman-protocol 0.1.0__tar.gz

haiman_protocol-0.1.0/.gitignore

@@ -0,0 +1,22 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.venv/
+venv/
+.env
+
+# Tooling caches
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+
+# OS / editor
+.DS_Store
+.idea/
+.vscode/

haiman_protocol-0.1.0/CHANGELOG.md

@@ -0,0 +1,23 @@
+# Changelog
+
+## 0.1.0 (unreleased)
+
+Initial standalone extraction of the Haiman protocol from the monorepo's
+in-process implementation.
+
+- `schemas/` — JSON Schema (Draft 2020-12) files for the v1 wire format:
+  common envelope + error + value schemas (tone.v1, topic.v1); the nine op
+  request payloads (handshake, propose, edit, accept, reject,
+  contribute-signal, query, handoff, notify); the three v1 typed handoff inner
+  payloads (engagement-flag-to-sdr, positive-reply-to-crm,
+  stalled-deal-reactivate).
+- `haiman_protocol` Python SDK — schema store/loader, payload/envelope/message
+  validation, the section 1.5 error taxonomy, vocabularies, and the canonical
+  cross-vendor `WireEnvelope`.
+- Tests: schema validity, golden positive examples, negative cases, an
+  anti-drift check that the Python vocabularies match the schema enums, and
+  envelope round-tripping.
+
+Not yet done (next): refactor the Haiman monorepo's `app/protocol.py` to import
+this package instead of carrying validation inline; formal conformance test
+suite; `did:web` hosting profile and VC schemas.

haiman_protocol-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Haiman
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

haiman_protocol-0.1.0/LICENSE-SCHEMAS

@@ -0,0 +1,16 @@
+Haiman protocol schemas — license notice
+========================================
+
+The JSON Schema files under `schemas/` are licensed under the
+Creative Commons Attribution 4.0 International License (CC-BY-4.0).
+
+SPDX-License-Identifier: CC-BY-4.0
+
+You are free to share and adapt the schemas for any purpose, including
+commercially, provided you give appropriate credit. Full license text:
+https://creativecommons.org/licenses/by/4.0/legalcode
+
+The reference SDK (everything under `src/`) is licensed separately under
+Apache-2.0; see the LICENSE file.
+
+Attribution: "Haiman protocol schemas, https://haiman.ai".

haiman_protocol-0.1.0/PKG-INFO

@@ -0,0 +1,118 @@
+Metadata-Version: 2.4
+Name: haiman-protocol
+Version: 0.1.0
+Summary: Open reference SDK and JSON Schemas for the Haiman personal-AI substrate protocol.
+Project-URL: Homepage, https://haiman.ai
+Project-URL: Source, https://github.com/haiman-ai/haiman-protocol
+Author-email: Haiman <carl@haiman.ai>
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: LICENSE-SCHEMAS
+Keywords: agent,did,haiman,personal-ai,protocol,verifiable-credentials
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Libraries
+Requires-Python: >=3.10
+Requires-Dist: jsonschema>=4.18
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# haiman-protocol
+
+Open schemas and reference SDK for the **Haiman protocol**: the contract that
+lets a person's AI and a service interoperate under scoped, revocable, audited
+grants.
+
+Haiman is the personal-AI substrate layer (the user owns the model; services
+are clients of it), sitting above MCP (AI consumes tools) and alongside A2A
+(agents coordinate). This repository is the **connective tissue**: the
+wire-format schemas and a Python binding for them.
+
+## Posture
+
+Open schema, open reference implementation, paid conformance authority:
+
+- **Schemas** (`schemas/`) are the open artifact, licensed **CC-BY-4.0**.
+  Anyone can read and implement against them.
+- **Reference SDK** (`src/haiman_protocol/`) is licensed **Apache-2.0**.
+- The certification mark, conformance test suite, and production grant-token
+  issuer infrastructure are operated by Haiman as the neutral conformance
+  authority. They are not in this repository.
+
+This is the OpenID Foundation / Bluetooth SIG / Khronos playbook: open the wire
+format, charge for the conformance authority. A schema-donation path to a
+neutral standards body is committed in the Haiman platform model.
+
+## What's here
+
+```
+schemas/
+  common/      envelope, error, and shared value schemas (tone.v1, topic.v1)
+  ops/         the nine v1 operations (request payloads)
+  handoffs/    typed inter-service handoff inner payloads
+src/haiman_protocol/
+  validate.py  validate payloads / envelopes / whole messages against the schemas
+  errors.py    the section 1.5 error taxonomy (9 semantic types)
+  optypes.py   vocabularies (op types, handoff types, notify events, enums)
+  envelope.py  the canonical cross-vendor wire envelope (DID + VC fields)
+  store.py     locates and loads the bundled schema files
+```
+
+The nine operations: `handshake`, `propose`, `edit`, `accept`, `reject`,
+`contribute-signal`, `query`, `handoff`, `notify`.
+
+## Install
+
+```bash
+pip install -e ".[dev]"   # editable, with test deps
+pytest
+```
+
+Requires Python 3.10+. The only runtime dependency is `jsonschema`.
+
+## Use
+
+```python
+from haiman_protocol import (
+    WireEnvelope, validate_payload, validate_message, SchemaInvalid,
+)
+
+# Validate just a payload by op type
+validate_payload("propose.v1", {
+    "instruction": "Draft a follow-up email.",
+    "structured_context": {"channel": "email"},
+})
+
+# Build and validate a whole message (envelope + payload, and for handoffs the
+# inner payload too)
+env = WireEnvelope(
+    op_type="propose.v1",
+    subject="did:web:user.haiman.ai:u:0193abcd",
+    scope_ref="scp_0193def",
+    service_certification="urn:haiman:vc:cert:0193sdr",
+    grant_credential="eyJhbGc...",
+    payload={"instruction": "Draft a follow-up email.",
+             "structured_context": {"channel": "email"}},
+).to_dict()
+validate_message(env)   # raises SchemaInvalid on a bad message
+```
+
+Validation failures raise `haiman_protocol.SchemaInvalid` (an error type in the
+section 1.5 taxonomy) with a readable message and a JSON Pointer to the
+offending node.
+
+## Versioning
+
+Schemas are named `op.vN`. Within a major version, adding optional fields is
+non-breaking and receivers ignore unknown fields. Breaking changes bump the
+version; N-1 is supported for 12 months after N ships. The SDK package version
+(`haiman_protocol.__version__`) is independent of the protocol schema
+generation (`haiman_protocol.PROTOCOL_VERSION`).
+
+## Status
+
+`v1` schemas, alpha. This is the standalone extraction of the protocol from the
+Haiman monorepo's in-process implementation; the design of record is the Haiman
+protocol specification.

haiman_protocol-0.1.0/README.md

@@ -0,0 +1,97 @@
+# haiman-protocol
+
+Open schemas and reference SDK for the **Haiman protocol**: the contract that
+lets a person's AI and a service interoperate under scoped, revocable, audited
+grants.
+
+Haiman is the personal-AI substrate layer (the user owns the model; services
+are clients of it), sitting above MCP (AI consumes tools) and alongside A2A
+(agents coordinate). This repository is the **connective tissue**: the
+wire-format schemas and a Python binding for them.
+
+## Posture
+
+Open schema, open reference implementation, paid conformance authority:
+
+- **Schemas** (`schemas/`) are the open artifact, licensed **CC-BY-4.0**.
+  Anyone can read and implement against them.
+- **Reference SDK** (`src/haiman_protocol/`) is licensed **Apache-2.0**.
+- The certification mark, conformance test suite, and production grant-token
+  issuer infrastructure are operated by Haiman as the neutral conformance
+  authority. They are not in this repository.
+
+This is the OpenID Foundation / Bluetooth SIG / Khronos playbook: open the wire
+format, charge for the conformance authority. A schema-donation path to a
+neutral standards body is committed in the Haiman platform model.
+
+## What's here
+
+```
+schemas/
+  common/      envelope, error, and shared value schemas (tone.v1, topic.v1)
+  ops/         the nine v1 operations (request payloads)
+  handoffs/    typed inter-service handoff inner payloads
+src/haiman_protocol/
+  validate.py  validate payloads / envelopes / whole messages against the schemas
+  errors.py    the section 1.5 error taxonomy (9 semantic types)
+  optypes.py   vocabularies (op types, handoff types, notify events, enums)
+  envelope.py  the canonical cross-vendor wire envelope (DID + VC fields)
+  store.py     locates and loads the bundled schema files
+```
+
+The nine operations: `handshake`, `propose`, `edit`, `accept`, `reject`,
+`contribute-signal`, `query`, `handoff`, `notify`.
+
+## Install
+
+```bash
+pip install -e ".[dev]"   # editable, with test deps
+pytest
+```
+
+Requires Python 3.10+. The only runtime dependency is `jsonschema`.
+
+## Use
+
+```python
+from haiman_protocol import (
+    WireEnvelope, validate_payload, validate_message, SchemaInvalid,
+)
+
+# Validate just a payload by op type
+validate_payload("propose.v1", {
+    "instruction": "Draft a follow-up email.",
+    "structured_context": {"channel": "email"},
+})
+
+# Build and validate a whole message (envelope + payload, and for handoffs the
+# inner payload too)
+env = WireEnvelope(
+    op_type="propose.v1",
+    subject="did:web:user.haiman.ai:u:0193abcd",
+    scope_ref="scp_0193def",
+    service_certification="urn:haiman:vc:cert:0193sdr",
+    grant_credential="eyJhbGc...",
+    payload={"instruction": "Draft a follow-up email.",
+             "structured_context": {"channel": "email"}},
+).to_dict()
+validate_message(env)   # raises SchemaInvalid on a bad message
+```
+
+Validation failures raise `haiman_protocol.SchemaInvalid` (an error type in the
+section 1.5 taxonomy) with a readable message and a JSON Pointer to the
+offending node.
+
+## Versioning
+
+Schemas are named `op.vN`. Within a major version, adding optional fields is
+non-breaking and receivers ignore unknown fields. Breaking changes bump the
+version; N-1 is supported for 12 months after N ships. The SDK package version
+(`haiman_protocol.__version__`) is independent of the protocol schema
+generation (`haiman_protocol.PROTOCOL_VERSION`).
+
+## Status
+
+`v1` schemas, alpha. This is the standalone extraction of the protocol from the
+Haiman monorepo's in-process implementation; the design of record is the Haiman
+protocol specification.

haiman_protocol-0.1.0/pyproject.toml

@@ -0,0 +1,54 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "haiman-protocol"
+description = "Open reference SDK and JSON Schemas for the Haiman personal-AI substrate protocol."
+readme = "README.md"
+requires-python = ">=3.10"
+license = "Apache-2.0"
+license-files = ["LICENSE", "LICENSE-SCHEMAS"]
+authors = [{ name = "Haiman", email = "carl@haiman.ai" }]
+keywords = ["haiman", "personal-ai", "protocol", "did", "verifiable-credentials", "agent"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Intended Audience :: Developers",
+  "Programming Language :: Python :: 3",
+  "Topic :: Software Development :: Libraries",
+]
+dependencies = ["jsonschema>=4.18"]
+dynamic = ["version"]
+
+[project.optional-dependencies]
+dev = ["pytest>=7"]
+
+[project.urls]
+Homepage = "https://haiman.ai"
+Source = "https://github.com/haiman-ai/haiman-protocol"
+
+[tool.hatch.version]
+path = "src/haiman_protocol/version.py"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/haiman_protocol"]
+
+# Ship the open schemas inside the wheel so importlib.resources can find them
+# at runtime when pip-installed. In editable / source checkouts the loader
+# falls back to the repo-root schemas/ dir (see store.schema_root()).
+[tool.hatch.build.targets.wheel.force-include]
+"schemas" = "haiman_protocol/schemas"
+
+[tool.hatch.build.targets.sdist]
+include = [
+  "src/haiman_protocol",
+  "schemas",
+  "tests",
+  "README.md",
+  "CHANGELOG.md",
+  "LICENSE",
+  "LICENSE-SCHEMAS",
+]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

haiman_protocol-0.1.0/schemas/common/envelope.schema.json

@@ -0,0 +1,53 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://haiman.ai/protocol/schemas/common/envelope.schema.json",
+  "title": "Haiman protocol common envelope (v1, cross-vendor wire form)",
+  "description": "Fixed envelope wrapping every protocol message. Identity is W3C-native: subject is a W3C DID; service_certification and grant_credential are W3C Verifiable Credentials. See the Haiman protocol specification section 1.3. Async result envelopes drop grant_credential and add a status field; the handshake op is the one op where scope_ref may be omitted. Unknown fields are ignored by receivers (forward-compatible), so additionalProperties stays permissive.",
+  "type": "object",
+  "required": ["op_id", "op_type", "timestamp", "subject", "payload"],
+  "properties": {
+    "op_id": {
+      "type": "string",
+      "description": "Idempotency key. UUID v7 in production; any UUID string accepted at the schema layer. Retries with the same op_id are no-ops at the receiver.",
+      "minLength": 1
+    },
+    "op_type": {
+      "type": "string",
+      "description": "op.vN format, e.g. propose.v1.",
+      "pattern": "^[a-z][a-z-]*\\.v[0-9]+$"
+    },
+    "timestamp": {
+      "type": "string",
+      "format": "date-time",
+      "description": "Sender's clock, ISO 8601. Receivers should not reject on skew alone."
+    },
+    "service_certification": {
+      "type": "string",
+      "description": "Compact reference (URN) to a W3C VC of type HaimanServiceCertificationCredential issued by Haiman as conformance authority. Required on requests; omitted on async results.",
+      "minLength": 1
+    },
+    "grant_credential": {
+      "type": "string",
+      "description": "User-issued, Haiman-signed W3C VC (JWT-VC compact form) proving this user authorised this service for these scopes. Present on requests; dropped on async result envelopes.",
+      "minLength": 1
+    },
+    "subject": {
+      "type": "string",
+      "description": "The user identifier as a W3C DID. v1 uses did:web; did:haiman reserved.",
+      "pattern": "^did:[a-z0-9]+:.+"
+    },
+    "scope_ref": {
+      "type": "string",
+      "description": "The specific granted scope this op operates within. Optional only for handshake."
+    },
+    "status": {
+      "type": "string",
+      "description": "Present on async result envelopes only.",
+      "enum": ["pending", "complete", "error"]
+    },
+    "payload": {
+      "type": "object",
+      "description": "Op-specific payload; validate against the matching ops/<op_type>.schema.json."
+    }
+  }
+}

haiman_protocol-0.1.0/schemas/common/error.schema.json

@@ -0,0 +1,43 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://haiman.ai/protocol/schemas/common/error.schema.json",
+  "title": "Haiman protocol error envelope (v1)",
+  "description": "Returned in place of a result when an op fails. See the Haiman protocol specification section 1.5. The error.type taxonomy maps one-to-one to an HTTP code and a retry posture.",
+  "type": "object",
+  "required": ["op_id", "op_type", "status", "error"],
+  "properties": {
+    "op_id": { "type": "string", "minLength": 1 },
+    "op_type": { "type": "string", "pattern": "^[a-z][a-z-]*\\.v[0-9]+$" },
+    "status": { "const": "error" },
+    "error": {
+      "type": "object",
+      "required": ["code", "type", "message"],
+      "properties": {
+        "code": {
+          "type": "integer",
+          "description": "HTTP status code for the semantic type."
+        },
+        "type": {
+          "type": "string",
+          "description": "Semantic error type. Drives retry behaviour.",
+          "enum": [
+            "uncertified",
+            "ungranted",
+            "scope_violation",
+            "schema_invalid",
+            "idempotency_conflict",
+            "not_found",
+            "rate_limited",
+            "unavailable",
+            "internal_error"
+          ]
+        },
+        "message": { "type": "string" },
+        "retry_after": {
+          "type": "integer",
+          "description": "Seconds; populated for rate_limited (and may be set for unavailable)."
+        }
+      }
+    }
+  }
+}

haiman_protocol-0.1.0/schemas/common/tone.v1.schema.json

@@ -0,0 +1,18 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://haiman.ai/protocol/schemas/common/tone.v1.schema.json",
+  "title": "tone.v1 value schema",
+  "description": "Common value schema for a tone result (e.g. query.v1 user.preferences.tone.default). See the Haiman protocol specification section 3.5. primary is drawn from a published vocabulary; modifiers are free-form short tags, unknown ones ignored gracefully.",
+  "type": "object",
+  "required": ["primary"],
+  "properties": {
+    "primary": {
+      "type": "string",
+      "description": "Enum from a published vocabulary (warm-direct, formal-precise, casual-friendly, ...). Not hard-enumed here: the vocabulary grows under minor revisions and receivers ignore unknown values."
+    },
+    "modifiers": {
+      "type": "array",
+      "items": { "type": "string" }
+    }
+  }
+}

haiman_protocol-0.1.0/schemas/common/topic.v1.schema.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://haiman.ai/protocol/schemas/common/topic.v1.schema.json",
+  "title": "topic.v1 value schema",
+  "description": "Common value schema for an engaged topic (e.g. query.v1 user.context.recent_topics). See the Haiman protocol specification section 3.5.",
+  "type": "object",
+  "required": ["label"],
+  "properties": {
+    "label": { "type": "string" },
+    "weight": { "type": "number", "minimum": 0, "maximum": 1 },
+    "last_engaged_at": { "type": "string", "format": "date-time" }
+  }
+}