six chapters. one source of truth.

§01overview

syen comply is a cryptographic audit ledger for ai decision systems. it records every ai action, human approval, and automated decision as a tamper-evident entry that is independently verifiable by auditors, regulators, and courts.

this guide covers installation, authentication, event ingestion, chain verification, and proof retrieval. a complete integration for a new event type takes under thirty minutes.

§02prerequisites

• python 3.10 or higher
• a running syen comply deployment via aws or azure marketplace
• your tenant credentials provided at subscription activation
• network access to your syen comply endpoint

§03installation

no custom sdk required. use the standard python requests library:

pip install requests

§04authentication

authenticate with the api to receive a bearer token. all subsequent requests use this token.

curl

curl -X POST https://api.syensystems.com/api/v1/attest \
  -H "Content-Type: application/json" \
  -d '{
    "tenant_id": "your-tenant-id",
    "agent_id": "your-agent-name",
    "agent_code_hash": "sha256-hash-of-your-agent-code"
  }'

# Returns: {"token": "Bearer ..."}

python

import requests

resp = requests.post(
    "https://api.syensystems.com/api/v1/attest",
    json={
        "tenant_id": "your-tenant-id",
        "agent_id": "your-agent-name",
        "agent_code_hash": "sha256-hash-of-your-agent-code"
    }
)
token = resp.json()["token"]
headers = {"Authorization": f"Bearer {token}"}

§05ingesting events

every ai action, decision, or system event is recorded with a single ingest() call. the event_class determines the category. event_type is a free-form string scoped within the class.

basic event

receipt = requests.post(
    "https://api.syensystems.com/api/v1/events",
    headers=headers,
    json={
        "event_class": "EXECUTION",
        "event_type": "credit.decision.made",
        "stream_id": "your-tenant-id:prod-us-east-1:credit-decisions",
        "payload": {
            "applicant_id": "app-991",
            "decision": "APPROVED",
            "score": 740
        }
    }
).json()

print(receipt["event_id"])          # unique event identifier
print(receipt["sequence_counter"])  # position in the chain

event with human decision surface

when a human reviewed and approved a decision, include the decision_surface to record what was shown, when, and what they decided.

receipt = requests.post(
    "https://api.syensystems.com/api/v1/events",
    headers=headers,
    json={
        "event_class": "EXECUTION",
        "event_type": "credit.decision.made",
        "stream_id": "your-tenant-id:prod-us-east-1:credit-decisions",
        "payload": {"applicant_id": "app-991", "decision": "APPROVED"},
        "decision_surface": {
            "explainability_artifact_hash": "sha256-of-artifact-shown",
            "human_decision": "APPROVE",
            "presentation_timestamp": "2026-03-20T14:00:00Z",
            "signoff_timestamp": "2026-03-20T14:00:03Z",
            "decision_complexity_tier": 2
        }
    }
).json()

# True if signoff was under the threshold for the complexity tier
print(receipt["velocity_flag_triggered"])

event with extended context

pass optional context fields to capture ai model provenance, infrastructure details, and compliance gate results.

receipt = requests.post(
    "https://api.syensystems.com/api/v1/events",
    headers=headers,
    json={
        "event_class": "EXECUTION",
        "event_type": "model.inference",
        "stream_id": "your-tenant-id:prod-us-east-1:model-runs",
        "payload": {"output": "APPROVED"},
        "context": {
            "trace_id": "abc-123",
            "model_version": "risk-engine-v2.1.0",
            "compliance_gate_result": "APPROVED",
            "pii_detected": False,
            "cloud_provider": "aws",
            "cloud_region": "us-east-1"
        }
    }
).json()

event with full context objects

for governed ai decisions, pass the optional context objects to satisfy all 10 proof elements. each object is independently optional. pass only the objects relevant to your event type.

receipt = requests.post(
    "https://api.syensystems.com/api/v1/events",
    headers=headers,
    json={
        "event_class": "EXECUTION",
        "event_type": "credit.decision.made",
        "stream_id": "your-tenant-id:prod-us-east-1:credit-decisions",
        "payload": {"applicant_id": "app-991", "decision": "APPROVED"},
        "policy_context": {
            "policy_id": "policy-credit-v3",
            "policy_version": "3.1.0",
            "framework_name": "NIST_AI_RMF",
            "requirement_id": "GOVERN-1.2",
            "policy_effect": "ALLOW",
            "exception_approved": False
        },
        "data_lineage": {
            "data_asset_id": "dataset-credit-bureau-2026-q1",
            "data_source_system": "snowflake",
            "contains_pii": True,
            "contains_financial": True,
            "consent_basis": "contractual_necessity",
            "data_classification": "confidential"
        },
        "ai_execution_context": {
            "model_provider": "anthropic",
            "model_name": "claude-sonnet-4-6",
            "model_version": "20250514",
            "prompt_hash": "sha256-of-prompt",
            "response_hash": "sha256-of-response",
            "agent_runtime": "langchain",
            "agent_decision_type": "recommendation",
            "agent_reversibility_flag": False,
            "inference_latency_ms": 340
        },
        "guardrail_context": {
            "kill_switch_checked": True,
            "kill_switch_result": "PASS",
            "approval_gate_result": "APPROVED",
            "sandbox_executed": False,
            "risk_score": 0.12,
            "override_invoked": False
        },
        "human_review_context": {
            "human_review_required": True,
            "review_decision": "APPROVE",
            "final_approver_id": "user-analyst-007",
            "review_latency_ms": 4200,
            "reviewer_role": "credit_analyst"
        },
        "outcome_context": {
            "decision_result": "APPROVED",
            "actual_action_taken": "credit.line.issued",
            "downstream_system_notified": "oracle-ebs",
            "rollback_possible": False,
            "financial_impact_usd": 25000.00
        }
    }
).json()

§06event classes

syen comply supports eleven event classes covering the full lifecycle of an ai-assisted workflow. EXECUTION and OUTCOME are required for initial integration.

§07verifying the chain

the verify endpoint confirms the chain has not been tampered with. run this after any bulk operation or on a schedule to confirm ongoing integrity.

result = requests.get(
    "https://api.syensystems.com/api/v1/verify",
    headers=headers,
    params={"stream_id": "your-tenant-id:prod-us-east-1:credit-decisions"}
).json()

if result["verified"]:
    print(f"Chain verified: {result['checked_count']} events")
else:
    print("Integrity failure detected. Contact sales@syensystems.com.")

§08retrieving proof

for any event, retrieve the full non-repudiable proof package. this includes cryptographic signatures, chain linkage, and the human decision surface if present. payload data is never returned.

event_id = receipt["event_id"]

proof = requests.get(
    f"https://api.syensystems.com/api/v1/proof/{event_id}",
    headers=headers
).json()

# proof is available for independent verification
# contact sales@syensystems.com for auditor verification documentation

§09external timestamp anchoring

syen comply performs daily anchoring of the chain to an external fips-compliant trusted timestamp authority. the anchor record is retrievable via the api and independently verifiable by any authorized auditor.

anchor = requests.get(
    "https://api.syensystems.com/api/v1/anchor/2026-03-20",
    headers=headers
).json()

print(anchor["anchor_status"])      # complete
print(anchor["anchor_created_at"])

# independent verification documentation available to
# enterprise and federal customers on request

§10api reference

all endpoints require a bearer token from POST /api/v1/attest except GET /api/v1/health.

§11decision complexity tiers

when a human review is recorded, the velocity flag fires if the signoff was faster than the threshold for the tier. the event is always recorded regardless of the flag.

§12production deployment

syen comply deploys on kubernetes via helm chart. production deployment documentation including infrastructure requirements, kms configuration, and security hardening guidelines is provided to customers during technical onboarding.

contact sales@syensystems.com to begin the onboarding process. enterprise and federal customers receive dedicated deployment assistance.

§13context objects

the following six context objects may be passed as optional fields on any event POST. each object is independently optional. fields within each object are optional unless marked required.

policy_context

data_lineage

ai_execution_context

guardrail_context

human_review_context

outcome_context

§14the 10 proof elements

syen comply is designed to satisfy 10 proof requirements that regulators, auditors, and courts apply to governed ai decisions. the table below maps each requirement to the api fields that must be present to satisfy it. an integration is considered complete when all 10 elements are populated for every governed event.

§15source system mapping

syen comply accepts event data from any upstream system via the /api/v1/events endpoint. the mappings below show which syen comply fields to populate from each source system category and which event_class to use.

§16support

• email: sales@syensystems.com
• aws marketplace: support available via listing page
• azure marketplace: support available via listing page
• enterprise and federal: dedicated technical account management