Human-AI Chat Interaction Observatory

Document library

The contract Ownership, consent and access What the numbers mean For a coding agent Not published

Published documentation

14 documents,
served from http://hwaichatanalysis.skoonline.org/docs/

Everything this deployment publishes about its own contract. Start with the integration handbook if you are writing code; come here for the document that answers a question the handbook only summarised.

Real-time integration guide → Handbook OpenAPI JSON

What the API accepts and returns.

The contract

Markdown Real-time chat integration API — start here http://hwaichatanalysis.skoonline.org/docs/realtime-chat-api.md The working document for building an integration: the streaming-chat mapping, the full field reference, all sixteen events, retry semantics, limits and a runnable client. JSON OpenAPI 3.1 contract (JSON, machine-readable) http://hwaichatanalysis.skoonline.org/docs/api.json For codegen, schema validation, or handing to a tool definition. Also served at /api.json. YAML OpenAPI 3.1 contract (YAML source) http://hwaichatanalysis.skoonline.org/docs/openapi.yaml The same contract, in the form it is authored and reviewed in. Markdown API reference http://hwaichatanalysis.skoonline.org/docs/api.md Every endpoint in one table, grouped by area, with the response envelopes and error codes.

Who the data belongs to, and who is allowed to read it.

Ownership, consent and access

Markdown Integration guide — ownership and consent model http://hwaichatanalysis.skoonline.org/docs/integration-guide.md Why your application never owns a thread, what a data owner is, and what consent version you are recording when you create one. Markdown Authentication, delegation and the ownership model http://hwaichatanalysis.skoonline.org/docs/authentication.md Token shape, the delegation claims, and how an internal owner key is derived from a subject. Markdown Who may read what, by role and scope http://hwaichatanalysis.skoonline.org/docs/authorization-matrix.md The complete role x resource matrix. Authentication establishes who; this decides what. Markdown Grants, scopes, revocation and audit http://hwaichatanalysis.skoonline.org/docs/research-consent.md How an owner shares a thread with a researcher, what each scope unlocks, and how revocation works. Markdown Data-handling obligations http://hwaichatanalysis.skoonline.org/docs/privacy-security.md What you must not send, what is redacted, and what you inherit by integrating.

Definitions, and the interpretations each measure does not support.

What the numbers mean

Markdown Every metric, and its prohibited interpretation http://hwaichatanalysis.skoonline.org/docs/metric-dictionary.md Read this before you display a single number. Each measure is defined alongside the interpretation it does not support. Markdown Speech-act taxonomy http://hwaichatanalysis.skoonline.org/docs/speech-act-taxonomy.md The categories a contribution is classified into, and what each one counts as evidence of. Markdown LCC — Learner's Characteristic Curves http://hwaichatanalysis.skoonline.org/docs/lcc-guide.md Layer 2 engine one: preconditions, the reference model, and reading a curve. Markdown ICCC — Individual Conversation Characteristics Curves http://hwaichatanalysis.skoonline.org/docs/iccc-guide.md Layer 2 engine two: per-participant collaboration curves, and why Social Impact is revisable. Markdown xAPI profile: verbs, activity types, extension IRIs http://hwaichatanalysis.skoonline.org/docs/xapi-profile.md What is emitted to a learning record store, with pseudonymous actors.

Hand to a program

The same library, machine-readable

Every document here is also listed at http://hwaichatanalysis.skoonline.org/docs as JSON, with a title, a description and an absolute URL — so an agent can enumerate the set rather than scrape this page.

curl -s http://hwaichatanalysis.skoonline.org/docs | jq -r '.documents[] | "\(.url)\t\(.title)"'
curl -s http://hwaichatanalysis.skoonline.org/docs/metric-dictionary.md
curl -s http://hwaichatanalysis.skoonline.org/api.json

The Markdown documents are served as source, so a browser may offer to save one rather than display it. curl them, or point a coding agent straight at the URL — which is what they are published for.

Deliberately absent

What is not published here

These describe how this deployment is built rather than how to integrate with it, so they are not served — a request for one is a plain 404. They live in the repository, and an operator can send you one.

Document	Why it stays internal
`architecture.md`	How this deployment is put together internally
`deployment.md`	How it is built, configured and released
`gcs-layout.md`	The object-store key space behind the API
`evaluation.md`	The internal evaluation harness for the semantic engines
`testing-interface.md`	The operator-facing testing interface

Research-integrity notice — it accompanies every analysis this API returns, and it constrains what any interface built on these documents may claim:
These measures describe observable and computationally inferred interaction patterns. They do not, by themselves, establish learning, mastery, cognitive effort, engagement, trust, factual quality, intelligence, personality, or causal influence. Such interpretations require external measures and empirical validation.