mcp-event-intelligence 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,80 @@
+# Changelog
+
+All notable public changes are documented here.
+
+## [0.1.0] - 2026-09-20
+
+Initial public reference release.
+
+### Standard MCP control plane
+
+- official TypeScript SDK v2 stdio server targeting MCP 2026-07-28;
+- read-only Event Intelligence tools exposed by default;
+- persistent mutation tools require explicit operator opt-in and confirmation IDs;
+- `server.json` + npm `mcpName` ownership metadata;
+- official MCP Registry schema/semantic validation in CI;
+- packed npm artifact smoke-tested for MCP entrypoints.
+
+### Launch visuals
+
+- rendered hero architecture SVG;
+- rendered durable-time/restart SVG;
+- rendered Inspector/provenance SVG.
+
+### Event ingestion and MCP Events boundary
+
+- experimental MCP Events discovery, `events/list`, and `events/poll` compatibility;
+- embedded host API discovers already-connected MCP clients from the harness registry;
+- no duplicate provider URL/token configuration or per-MCP Event Intelligence setup;
+- tools-only MCPs are ignored while Events-capable MCPs are attached automatically;
+- dynamic registry refresh plus low-level attach/detach support;
+- persistent opaque cursors and restart-safe event deduplication;
+- GitHub provider webhook mapping into MCP EventOccurrence and automatic composite fan-in.
+
+### Durable trigger engine
+
+- `allOf`, `anyOf`, `sequence`, and `count`;
+- deterministic same-value correlation;
+- optional semantic correlation;
+- persistent partial/matched/fired/expired state and replay safety;
+- agent-authored trigger control with source scoping, advertised-field validation and approval gating;
+- no bundled OpenAI planner: the surrounding agent authors the structured trigger directly.
+
+### Temporal reasoning
+
+- calendar-aware conditions with IANA timezones;
+- `absence`, `not`, `unless`, `after`, `until`, `debounce`, `threshold`, `rate`, and `distinct`;
+- durable deadlines that progress without a new provider event;
+- restart recovery and DST-aware tests.
+
+### Runtime continuations
+
+- signed refs-only wake packets;
+- one in-process harness wake dispatcher can route continuations to multiple agents;
+- optional signed callback targets for standalone deployments;
+- runtime receipts, retry/dead-letter lifecycle, and idempotency;
+- trigger lifecycle policies: one-shot, max firings, cooldown, expiry, lease, update, delete, and self-retirement.
+
+### Derived events and contracts
+
+- trigger composition through immutable derived events;
+- flattened root provenance and direct-parent lineage;
+- cycle detection and recursion depth limits;
+- versioned derived-event contracts with canonical schema fingerprints;
+- compatibility preflight and ambiguous-consumer rejection.
+
+### Observability and verification
+
+- deterministic Trigger Inspector with why-fired / why-not-fired state;
+- isolated trigger simulation;
+- full-system black-box acceptance covering signed wake, contract evolution, replay, and restart during a pending deadline;
+- real GitHub provider regression verified in the persistent environment.
+
+### Known limitations
+
+- MCP Events support targets an experimental design and is not a finalized MCP specification;
+- automatic MCP discovery requires the embedding harness to expose its connected-client registry through the small host adapter interface;
+- JSONL persistence is single-writer and reference-grade;
+- no multi-replica / HA storage backend is included;
+- the v0.1 MCP control plane is stdio-only; a Streamable HTTP control-plane transport is not included;
+- Stateful Facts / current-state materialization is intentionally deferred.

package/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 MCP Event Intelligence contributors
+
+   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.

package/README.md

@@ -0,0 +1,298 @@
+# MCP Event Intelligence
+
+> Durable temporal event intelligence for sleeping agents.
+
+[![CI](https://github.com/sarooo17/event-intelligence/actions/workflows/ci.yml/badge.svg)](https://github.com/sarooo17/event-intelligence/actions/workflows/ci.yml)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+
+MCP Event Intelligence is an experimental event runtime for agents that need to react to **future conditions over multiple event sources** without keeping an LLM or agent loop alive.
+
+The primary integration model is **embedded and host-owned**: the agent host keeps its existing MCP clients, transports, OAuth sessions and provider credentials. Event Intelligence receives a reference to the host's MCP registry, discovers the already-connected clients automatically, and uses only the Events-capable ones.
+
+<p align="center">
+  <img src="docs/assets/hero-architecture.svg" alt="MCP Event Intelligence architecture: event sources flow into durable composite and temporal reasoning, derived versioned events, and runtime wakeups." width="100%" />
+</p>
+
+An agent can express an intent such as:
+
+> When this PR is merged, the production deploy succeeds, and no error is observed for 10 minutes, wake this task and review the release.
+
+Event Intelligence persists that continuation independently of the model, waits for the world to satisfy it, and wakes the host only when necessary.
+
+## Embed it in an existing agent host
+
+After publication:
+
+```bash
+npm install mcp-event-intelligence
+```
+
+Pass the harness-level MCP registry once — not every MCP one by one:
+
+```js
+import {
+  createEventIntelligenceHost,
+  createMcpRegistryAdapter,
+} from 'mcp-event-intelligence/host';
+
+const ei = await createEventIntelligenceHost({
+  dataDir: './data',
+  mcpRegistry: createMcpRegistryAdapter({
+    listConnections: () => host.mcp.listConnections(),
+    subscribe: (refresh) => host.mcp.onConnectionsChanged(refresh),
+  }),
+  wake: async (packet) => {
+    const receipt = await host.resume(packet.target, packet);
+    return { runtimeReceiptId: receipt.id };
+  },
+});
+```
+
+Event Intelligence enumerates the host registry automatically. GitHub, Gmail, private/company MCPs and future connections do not need to be configured again inside EI. Tools-only MCPs remain available to the agent and are ignored by the Events layer; Events-capable MCPs are attached automatically.
+
+## What v0.1 implements
+
+### Host-owned event sources
+
+- automatic discovery from the host's existing MCP registry;
+- reuse of already-connected MCP clients without duplicate credentials;
+- experimental MCP Events capability discovery;
+- `events/list` and `events/poll`;
+- persistent opaque cursors;
+- automatic event-source registration;
+- dynamic attach/detach of host MCP clients;
+- provider-native compatibility adapters such as GitHub webhooks.
+
+### Composite and temporal triggers
+
+- `allOf`, `anyOf`, `sequence`, `count`;
+- deterministic same-value correlation;
+- optional semantic correlation;
+- `absence`, `not`, `unless`, `after`, `until`;
+- `debounce`, `threshold`, `rate`, `distinct`;
+- calendar-aware conditions with IANA timezones;
+- durable deadlines that continue even when no new provider event arrives.
+
+### Agent-authored continuations
+
+- event-source discovery;
+- agent-authored structured trigger definitions;
+- deterministic validation against real source schemas and advertised fields;
+- approval-gated persistent mutations;
+- one-shot, cooldown, max-firings, expiry, leases, update and delete.
+
+### Derived events and composition
+
+Triggers can emit immutable higher-level events instead of waking an agent:
+
+```text
+pr.merged + deploy.succeeded
+              ↓
+        release.ready@1
+              +
+       manager.approved
+              ↓
+       rollout.allowed@1
+              ↓
+          runtime wake
+```
+
+Derived events preserve refs-only lineage to their direct parents and flattened root evidence.
+
+<p align="center">
+  <img src="docs/assets/provenance-inspector.svg" alt="Rendered Trigger Inspector and flattened provenance example." width="100%" />
+</p>
+
+### Versioned contracts
+
+Derived event names are versioned contracts such as `release.ready@1`.
+
+- first producer establishes the canonical schema;
+- compatible producers may join the same contract version;
+- incompatible schemas fail before trigger persistence;
+- multiple versions may coexist;
+- ambiguous unversioned consumers fail closed;
+- every occurrence carries a schema fingerprint.
+
+### Host or callback wake
+
+An embedded harness can provide one in-process wake dispatcher that routes by `target.runtime`, `target.kind` and `target.id`; runtime-specific handlers remain available as a lower-level option. A standalone deployment can instead use signed HMAC callbacks. Both paths return a stable `runtimeReceiptId`.
+
+## Why this exists
+
+MCP Events is concerned with the event transport/subscription boundary. Event Intelligence explores the layer **above transport**:
+
+- how an agent declares a future condition;
+- how multi-event state survives while the agent sleeps;
+- how absence/time becomes an event;
+- how higher-level facts are derived without invoking a model;
+- how those facts can be safely composed;
+- how a host resumes an agent effectively once in the validated scenarios.
+
+This project does **not** propose a replacement for MCP Events and does not claim to be an official MCP extension.
+
+## AI and API keys
+
+Event Intelligence has one optional AI boundary: **semantic correlation**.
+
+- `TYPESAFE_API_KEY` enables the bundled TypeSafe Jev evaluator when a trigger explicitly requests semantic correlation.
+- embedded hosts may inject a compatible `semanticEvaluator` instead.
+- there is no bundled OpenAI planner and no OpenAI API dependency.
+
+The agent/harness is already responsible for reasoning and can author a structured trigger directly from `event_sources_list` / the discovered schemas. Deterministic correlation, temporal logic, persistence, derived events and wake delivery require no model API.
+
+## Full-system acceptance
+
+The v0.1 acceptance suite verifies:
+
+- host-owned MCP client → event discovery/poll → composite match → in-process wake;
+- provider-neutral events → composite match → derived event → derived composition → signed runtime wake;
+- contract schema evolution and ambiguity rejection;
+- refs-only root provenance;
+- replay without duplicate derived events or wakes;
+- process shutdown while a temporal deadline is pending;
+- restart on the same datastore after the deadline;
+- wake recovery **without a new provider event**;
+- hash-linked audit verification.
+
+A separate live regression also verified real GitHub webhook ingress into the MCP EventOccurrence / composite fan-in path.
+
+## Standalone reference service
+
+### Requirements
+
+- Node.js 22+
+- no external database for the reference setup
+
+```bash
+git clone https://github.com/sarooo17/event-intelligence.git
+cd mcp-event-intelligence
+npm ci
+npm run check
+
+export SERVICE_AUTH_TOKEN="$(openssl rand -hex 32)"
+npm start
+```
+
+Then:
+
+```bash
+curl http://127.0.0.1:3000/readyz
+```
+
+The standalone service supports manual/provider-native event ingress. It does not own arbitrary MCP connections; host-owned MCP reuse belongs to the package integration above.
+
+### Docker
+
+```bash
+docker build -t mcp-event-intelligence:0.1.0 .
+
+docker run --rm \
+  -p 3000:3000 \
+  -v mcp-event-intelligence-data:/data \
+  -e SERVICE_AUTH_TOKEN="$(openssl rand -hex 32)" \
+  mcp-event-intelligence:0.1.0
+```
+
+## Optional MCP control plane
+
+The package also exposes a standard **MCP stdio** control plane through the official TypeScript SDK v2:
+
+```bash
+npx mcp-event-intelligence mcp
+```
+
+Read/non-mutating tools are exposed by default, including `event_sources_list`, inspection, simulation, contracts and runtime status. An agent uses those discovered source schemas to author the structured definition passed to `trigger_create`.
+
+Persistent trigger mutations are only registered when the operator explicitly enables `MCP_WRITE_ENABLED=true`, and each mutation still requires a `confirmationId`. The MCP server is a control-plane adapter; it is **not** a gateway through which the host's other MCP servers must be reconnected.
+
+See [docs/QUICKSTART.md](docs/QUICKSTART.md) and [docs/MCP-REGISTRY.md](docs/MCP-REGISTRY.md).
+
+## Configuration
+
+Standalone/core environment variables:
+
+| Variable | Required | Purpose |
+| --- | --- | --- |
+| `SERVICE_AUTH_TOKEN` | yes for protected HTTP APIs | bearer token for control-plane endpoints |
+| `DATA_DIR` | no | persistent JSONL directory, default `./data` |
+| `PORT` | no | HTTP port, default `3000` |
+| `ENVIRONMENT_ID` | no | environment boundary |
+| `RUNTIME_WAKE_TARGETS_JSON` | no | signed standalone runtime callbacks |
+| `GITHUB_WEBHOOK_SECRET` | no | verify GitHub webhook ingress |
+| `TYPESAFE_API_KEY` | no | bundled TypeSafe Jev semantic evaluator |
+
+Embedded hosts pass one MCP registry adapter. Event Intelligence discovers already-connected clients from that registry; provider MCP connection settings are not duplicated inside EI.
+
+## Architecture
+
+The detailed execution model, clocks, lifecycle, persistence and trust boundaries are documented in [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md).
+
+## Important semantics
+
+### Event-time vs processing-time
+
+Normal event windows use event `occurredAt`.
+
+Absence/deadline progression uses Event Intelligence processing time. This separation is explicit and tested.
+
+<p align="center">
+  <img src="docs/assets/durable-time-restart.svg" alt="Rendered durable-time timeline showing a deadline surviving process shutdown and firing after restart." width="100%" />
+</p>
+
+### Effectively-once runtime activation
+
+The implementation does not claim theoretical distributed exactly-once delivery.
+
+It uses stable wake IDs, persistence, deduplication, runtime receipts and replay handling to provide effectively-once runtime activation in the validated reference scenarios.
+
+### Derived event vs current state
+
+A derived event says **what became true at a point in history**.
+
+v0.1 intentionally does not implement a mutable current-state/facts database.
+
+## Security
+
+Read [SECURITY.md](SECURITY.md) and [docs/SECURITY-MODEL.md](docs/SECURITY-MODEL.md).
+
+In embedded mode, the host retains MCP authorization and credentials; Event Intelligence discovers only the client objects exposed through the host-provided MCP registry. The v0.1 reference store is JSONL and single-writer.
+
+## MCP compatibility status
+
+There are two separate MCP boundaries:
+
+- **event ingress**: host-owned, already-connected MCP clients exposing experimental Events, plus provider-native adapters;
+- **control plane**: optional standard MCP **stdio** server built on the official TypeScript SDK v2 and targeting protocol revision 2026-07-28.
+
+Registry identity:
+
+```text
+io.github.sarooo17/event-intelligence
+```
+
+`server.json` is validated with the official `mcp-publisher validate` command in CI. MCP Events itself remains experimental and may change as the Triggers & Events work evolves.
+
+## Project status
+
+**v0.1 reference implementation / experimental.**
+
+The architecture is implemented and exercised end-to-end. Remaining work is primarily production storage/HA, broader host/provider evidence, scale benchmarks and upstream feedback.
+
+## Example
+
+See the [release-gate example](docs/examples/release-gate.md) for a composed future-condition flow using durable time, derived events and targeted wake.
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+Contributions are especially useful around host adapters, MCP Events compatibility, temporal semantics, production persistence, security review and reproducible provider integrations.
+
+## License
+
+Apache License 2.0. See [LICENSE](LICENSE).
+
+## Disclaimer
+
+This is an independent open-source project. It is not an official Model Context Protocol specification and is not affiliated with or endorsed by the MCP maintainers.

package/SECURITY.md

@@ -0,0 +1,42 @@
+# Security Policy
+
+## Supported versions
+
+The public reference implementation is currently pre-1.0.
+
+| Version | Supported |
+| --- | --- |
+| 0.1.x | Yes |
+| < 0.1 | No |
+
+## Reporting a vulnerability
+
+Please do **not** open a public issue with exploit details, credentials, private payloads, or reproduction secrets.
+
+Use GitHub's private vulnerability reporting / security advisory flow for this repository when available. If the repository UI does not expose a private reporting option, open a minimal public issue asking the maintainer for a private contact channel **without including vulnerability details**.
+
+Useful reports include:
+
+- affected version/commit;
+- impacted endpoint, protocol object, or runtime adapter;
+- minimum reproduction;
+- security impact;
+- whether the issue requires authenticated access;
+- suggested mitigation, if known.
+
+## Security boundaries
+
+Event Intelligence v0.1 is a reference implementation, not a hardened multi-tenant hosted service.
+
+Important defaults and constraints:
+
+- protected control-plane endpoints require `SERVICE_AUTH_TOKEN`;
+- GitHub ingress verifies provider HMAC when configured;
+- runtime wake packets are HMAC-signed and runtime targets are operator-configured;
+- arbitrary public HTTP wake targets are rejected;
+- derived-event lineage is refs-only by default;
+- audit records are hash-linked and tamper-evident, not tamper-proof;
+- the JSONL store is single-writer and not safe for horizontal multi-replica deployment;
+- secrets belong in environment variables / secret managers, never committed files.
+
+See `docs/SECURITY-MODEL.md` for the architectural model.

package/bin/mcp-event-intelligence.mjs

@@ -0,0 +1,52 @@
+#!/usr/bin/env node
+
+const args = process.argv.slice(2);
+const flags = new Set(args);
+
+if (flags.has('--version') || flags.has('-v')) {
+  console.log('0.1.0');
+  process.exit(0);
+}
+
+if (flags.has('--help') || flags.has('-h')) {
+  console.log(`MCP Event Intelligence v0.1
+
+Durable temporal event intelligence for sleeping agents.
+
+Usage:
+  mcp-event-intelligence          Start the HTTP reference service
+  mcp-event-intelligence mcp      Start the standard MCP stdio control plane
+  mcp-event-intelligence --mcp    Same as "mcp"
+
+MCP stdio mode:
+  DATA_DIR=./data
+  MCP_WRITE_ENABLED=false         Read-only by default
+  MCP_OWNER_ID=local-user
+  MCP_ACTOR_ID=mcp-agent
+  RUNTIME_WAKE_TARGETS_JSON='{}'
+
+HTTP service:
+  SERVICE_AUTH_TOKEN=<random secret>
+  PORT=3000
+  DATA_DIR=./data
+
+Optional integrations:
+  TYPESAFE_API_KEY=<key>          Optional TypeSafe Jev semantic evaluator
+  GITHUB_WEBHOOK_SECRET=<secret>  GitHub webhook verification
+  RUNTIME_WAKE_TARGETS_JSON='{}'  Signed standalone runtime callbacks
+
+Embedded hosts:
+  import { createEventIntelligenceHost } from 'mcp-event-intelligence/host'
+  Pass the harness MCP registry once; EI discovers Events-capable clients automatically.
+
+Important:
+  stdout is reserved for MCP JSON-RPC in stdio mode.
+`);
+  process.exit(0);
+}
+
+if (args[0] === 'mcp' || flags.has('--mcp')) {
+  await import('../scripts/mcp-stdio.mjs');
+} else {
+  await import('../scripts/service.mjs');
+}