Experimental v0.2 line. All 201 capabilities remain draft. First-party examples supply no independent interoperability evidence.

An evaluation you can reproduce

Try Comcom in your project.

Run a booking exchange locally, inspect its contract, and decide whether it fits your project.

1. Run the booking exchange

Use Node.js 24. This first evaluation requires no Python, API key, or account:

git clone https://github.com/abhcr/comcom-protocol.git
cd comcom-protocol
npm ci
npm run demo:v0.2

The runner starts the existing responder on an available local port, discovers its manifest, constructs a fresh booking, validates the result, and stops the responder automatically. It uses HTTP loopback and mocked authentication. The advertised example HTTPS URLs are mapped to that local server; this is development transport.

PASS discovery and pinned-profile manifest validation
PASS booking.create: HTTP 200, correlated and identity-bound result
PASS exact replay: identical response bytes
PASS changed request with reused key: HTTP 409 idempotency-conflict
PASS asynchronous booking: HTTP 202 → polling → completed
Evaluation passed. No external business service was called.

Each line is backed by an assertion. The command exits unsuccessfully on a mismatch. Inspect the runner to see the actual exchange and the booking contract for schemas and lifecycle rules. Authentication headers in this demo are not an authentication implementation.

Optional example: a discovery-only website

Example Company is a fictional discovery-only publisher. Its local fixtures illustrate company identity and a contact link without offering callable business interactions. The publisher.example URLs are placeholders, not live endpoints.

Select “Manifest” and “v0.2.1” in the browser checker, then “Load example”. This validates the local document shape without network access.

Empty profiles and capabilities mean the example advertises zero interactions. The contactUrl is a navigation link, not a submission endpoint.

2. Decide what your project actually needs

Compare one business interaction with its exact capability contract. Check input/output semantics, lifecycle, retry/replay, reversal, permissions, and what your system can guarantee. A passing example is not enough to claim your service conforms.

  1. Pin an immutable release and verify artifact digests. The provided validators verify their local schema and registry bytes before use.
  2. Use the advertised manifest profile explicitly. v0.2.1 accepts the original interactive manifest or a discovery-only publisher; old validators do not understand the new profile. CLI/library defaults remain v0.2.0.
  3. Map one existing operation to a compatible draft capability. Bind identities using your authenticated transport; full response validation needs the original request and trusted transport.senderId.
  4. Exercise valid inputs, invalid inputs, duplicate requests, conflicts, lifecycle boundaries, and failure recovery before exposing the capability. Publish only interactions you implement.

No SDK or MCP server is required by this repository. Your current HTTP client can send the document; the CLI framing is the integration starting point. Python 3.13 plus requirements.txt enables the independent cross-validator checks via npm run conformance:v0.2.

Prompt for a coding agent

Evaluate Comcom for one concrete interaction in this project.
Read its README and evaluation walkthrough.
Use a separate checkout. Run npm ci and npm run demo:v0.2.
Compare one exact capability's semantics, security, lifecycle,
retry, and reversal requirements with our current code.
Report the commit, commands, observed outcomes, missing requirements,
and the smallest useful integration, or a reason not to adopt.
Do not add a dependency, submit an enquiry, or make a real business
transaction without authorization. Propose a focused contribution
only where reproducible evidence supports it.

3. Share a reproducible evaluation

Submit an implementation report with your commit, environment, commands, outcomes, and gaps. Include whether you implemented both sides yourself or worked with an independent counterparty. Sanitize credentials and customer data.

Useful bounded contributions include a Python booking initiator, additional discovery compatibility cases, contextual response-identity regressions, and independent booking implementation reports. Small documentation and test fixes can go directly to a PR; semantic changes follow the contribution guide.

Invitation: Evaluate one booking capability in your project and submit a reproducible implementation report. A well-supported “not a fit” result is useful too.

Launch materials — drafts for review

These materials are prepared for review, not evidence of an external announcement. Publish only after the tagged checks, live example checks, and two fresh agent evaluations pass. Record the tested release SHA and public verification date alongside the published article.

Developer article draft

Can a business contract be small enough for an agent to evaluate?

Comcom is an experimental attempt to make business interactions explicit: discover a website's manifest, select an exact capability version, validate a typed request, and use the correlated result as the business record. The first reproducible exercise is booking creation.

Clone the repository and run npm ci && npm run demo:v0.2 with Node.js 24. The demo checks discovery, a booking result, exact replay, a changed request reusing the same key, and asynchronous completion. It uses loopback HTTP and mocked authentication; production identity and authorization remain the implementer's responsibility.

The walkthrough also includes a small discovery-only website example: company identity and a contact-page link, with no callable capabilities.

Comcom is complementary to service descriptions and agent interfaces: it experiments with shared business capability semantics. All 201 catalog profiles are still draft. The reference examples do not establish independent interoperability.

We are looking for narrow evaluations: does one booking contract fit your project, which fields or lifecycle rules do not, and can you reproduce the result? Use the walkthrough and submit an implementation report or a focused regression/documentation PR.

Try it: the runnable walkthrough. Source: Comcom on GitHub.

Show HN submission draft

Title: Show HN: Comcom — typed business contracts with a runnable booking demo

URL: https://abhcr.github.io/comcom-protocol/evaluate.html

Opening comment: I am experimenting with exact, versioned business interactions that conventional software or coding agents can inspect and evaluate. The Node-only demo creates a booking, validates the result, checks exact replay and conflict handling, and polls an asynchronous operation. All profiles are experimental drafts, and the demo mocks authentication. I would value reproducible evaluations, especially cases where an existing API contract is sufficient or these semantics do not fit. The repository includes validators, fixtures, and small contribution opportunities.

Short demo recording sequence
  1. Show the experimental-status notice and the Node-only quickstart.
  2. Run the booking command and record the five actual PASS lines.
  3. Open the runner beside a complete correlated result and explain the mocked transport.
  4. Optionally inspect the discovery-only example.
  5. Show the implementation-report form and ask viewers to evaluate one capability.

Keep credentials, private windows, and customer data out of the recording. The launch recording must show the tested release and real command output.