Cells / Examples

Operating history

Classify an event log into an operational pattern with bounded output.

Examplev1.1.0Operations
TRY THIS CELL

Ask within the boundary.

Example

Use the declared input, choose permitted fields, and inspect the recorded answer.

Request
Return fields & access
Requested return fields

Access expires

Run a request to inspect its result.
Execution details

The visible rules process text in this browser. Policy, lifetime, access and rolling disclosure checks apply. Each explicit execution creates one redacted record. Editing, presets and animation do not execute or spend disclosure allowance.

Task → Permitted answer
Owner-controlled boundary
  1. service started
  2. health check passed
  3. request completed
↓ Event pattern check

Inspect the supplied event sequence.

Output boundaryRequested fields only

The source remains inside. The answer crosses only after its checks.

Your result

Run a request to inspect its result.

Your answer and its record will appear together.
operating-history / OverviewCapability policy

Use the answer. Keep the source.

Classify supplied operational log text.

What this Cell defines

A Cell is a revocable execution boundary. Its Manifest describes the accepted input, allowed result fields, withheld information, request lifetime and cumulative disclosure limit.

How it works

Count case-insensitive error, failed, timeout, panic and critical tokens. Three or more signals classify a repeated incident; one or two classify an isolated incident; none classifies normal sample operation.

Execution details

This example analyzes supplied text locally in your browser. Its rules are public. It does not connect to an owner’s private source, execute submitted code, or establish a confidential runtime.

Protocol and roles Privacy boundaries