Maple Quality Agent

Authenticated gradings

The most recent decisions of the agent gateway, newest first: gradings, and sensor readings that a relay agent submitted for a lot. Each was made for an agent that presented its client certificate; each signature is checked in your browser. Visitors cannot grade: an agent grades by calling https://agents.cequs.com/grade with its certificate (deploy/agent-gateway/grade.sh).

Loading signed decisions…

A lot must be registered in the grading database, with its jurisdiction. Each barrel's Raman sample, Brix reading and inspection finding come from that database, never from the caller, and are not published except as part of a signed grading above. A barrel with mold observed at inspection, or below the Brix minimum, is rejected and gets no grade. An agent may grade only lots from a jurisdiction where it holds a current grant.

Portable Raman sample

Synthetic demonstration data shaped around the Xiao et al. workflow: Raman spectrum plus reference antioxidant indicators. It is not experimental paper data.

Sample

How a grading is authenticated

The agent connects to agents.cequs.com over TLS 1.3 and presents its client certificate. Apache refuses any certificate not issued by the agent CA.
The gateway binds the certificate's fingerprint to exactly one agent in the live directory (c=US, and c=CA through the link to the second server), and requires it to be active, to have a proofed accountable person, and to hold a current maple.lot.grade.propose grant in the lot's own jurisdiction.
Only then does the gateway ask the n8n workflow, on the same server, to grade the lot. n8n is not reachable from the internet, and it accepts the request only with a secret the gateway holds; the agent it grades for is the one the certificate proved, never one a caller named.
The gateway signs the decision and the grading result (Ed25519) into a hash-chained log. This page checks each signature.

The directory is OpenLDAP, read over LDAPS on loopback with its certificate pinned; the browser never sees a directory credential.

Live mTLS: agents.cequs.com

Loading the latest decision…

Latest decision: —
Decided at: —
Authenticated agent: —
Accountable human: —
Sponsor (unverified claim): —
Certificate SHA-256: —
Certificate expiry: —
Grant: —
Requested scope: —
Signature: —

An agent presents its certificate to https://agents.cequs.com/grade over TLS 1.3; a connection without a certificate from the agent CA is refused in the handshake. The gateway binds the certificate to one agent in the live directory and checks its grant, then signs the decision. This card shows the latest one, from /agent-gateway/status, and checks its Ed25519 signature in your browser. The browser never holds the agent private key.

Security rationale: Mutual authentication of agents is expected to become relevant to proposed EU legislation. Because Quebec trades with the EU, this page demonstrates a higher-security agentic workflow. A production deployment would use CA-issued certificates as part of an authentication design evaluated against applicable NIST SP 800-63B AAL3 requirements, together with human-user YubiKeys where appropriate. The author has previously implemented mTLS at IHE International for healthcare application processes. Ordinary web traffic commonly uses TLS 1.3; this demonstration adds mutual TLS using the certificate-based client authentication described in IETF RFC 8446. The YubiKey statement describes the current testing setup for Frontier AI cybersecurity-model functionality and is not a claim of endorsement by any organization.

n8n grading workflow (live)

Called only by the agent gateway, with its shared secret, for an agent the gateway has authenticated (until 9 October 2026 the webhook was public and took a claimed agent identifier) → agent looked up in LDAP → its authorization grant looked up → status, scope and grant-window check → allow or deny, the same fail-closed shape as the mTLS demonstration → if allowed, the lot read from the PostgreSQL grading database, through a read-only view (inspection results are kept there, not in LDAP and not on this site) → each barrel rejected if mold was observed at inspection or its Brix is below the minimum, otherwise graded from its own Raman sample. An unregistered lot is refused. Authorization is read only from the grant entry, never from the agent entry; being authorized to propose a grade does not make a barrel pass inspection. The workflow is in the repository with tests (n8n/maple-agent-grading-workflow.json) and has run on cequs.com since 2026-10-07. An earlier hosted workflow was never committed and could not be reviewed (SOFTWARE_DEFECTS.md, SEC-2026-09-19-03); the fixture-backed security/directory-policy/ that replaced it remains as an offline reference.