Empirica

We Gave AI a Mirror. Now It Measures What It Believes.

Epistemic infrastructure for AI — measurement, memory, and calibration across sessions.

Empirica tracks what AI knows, gates what it does, and compounds learning across session boundaries. It measures the gap between what AI predicts and what's true — making AI agents measurably more reliable.

Training & Guides | CLI Reference | Architecture

Important: Empirica is an AI measurement framework. It has no cryptocurrency, token, coin, or blockchain component. Any token using the Empirica name (including "$EMPIRICA" on Solana) is unauthorized and not affiliated with this project or Empirica AI GmbH.

The Problem

AI coding agents today have no self-awareness about what they know:

Forgets between sessions — same questions, same dead ends, every time
Acts before understanding — edits your code without knowing the architecture
Can't tell you when it's guessing — no distinction between knowledge and confabulation
No audit trail — reasoning evaporates with the context window

What Empirica Does

Capability	What You Experience
Measures before acting	AI investigates your codebase before touching it. The Sentinel gate blocks edits until understanding is demonstrated
Remembers across sessions	Findings, dead-ends, and learnings persist in a 4-layer memory system. Session 3 starts where Session 2 left off
Prevents confident mistakes	The CHECK gate uses domain-aware thresholds scaled by criticality — cybersec/high is stricter than default/low
Shows confidence in real-time	Live statusline in your terminal: `[empirica] ⚡94% ↕70% │ 🎯3 │ POST 🔍92% │ K:95% C:92%`
Calibrates against reality	Three-vector model: self-assessed, observed (from deterministic checks), and AI-reasoned grounded state with rationale. Domain compliance loops iterate until all checks pass
Tracks your codebase	Temporal entity model auto-extracts functions, classes, and imports from every file edit — the AI knows what's alive and what's stale
Works through natural language	You describe tasks normally. The AI operates the measurement system automatically
Optional: coordinates with peer AIs	Cross-Claude mesh via Cortex (opt-in) — peer AIs propose work, ECO accepts/declines, completion handshakes carry commit SHAs. A persistent listener wakes idle sessions on inbox events. Empirica core works standalone without this — see Cross-AI Mesh below for the ecosystem layer

How You Use It

You talk to your AI normally. Empirica works in the background:

You:      "Fix the authentication bug in the login flow"

Empirica: [AI investigates → logs findings → passes Sentinel gate → implements fix → measures learning]

You see:  ⚡87% ↕70% │ 🎯1 │ POST 🔍85% │ K:88% C:82% │ Δ +K

You direct. The AI measures.

Empirica's CLI has 240+ commands spanning investigation, measurement, calibration, and memory — like a cockpit instrument panel. You don't need to learn any of them. The AI reads the instruments, operates the controls, and reports back in natural language. The statusline gives you the flight data at a glance.

For power users, direct CLI access is always available: empirica goals-list, empirica calibration-report, empirica project-search --task "...", and more.

Learn the full workflow: getempirica.com has interactive training, guides, and deep explanations of every concept.

Quick Start

Install + Claude Code (Recommended)

pip install empirica
empirica setup

Then just start working. The hooks, Sentinel, system prompt, statusline, and MCP server are all configured automatically.

empirica setup --harness picks the harness. It resolves from --harness, else $EMPIRICA_HARNESS, else claude-code. An unsupported harness is refused by name and nothing is written — previously it wrote ~/.claude/ regardless and reported success, which on any other harness configured a path that harness never reads.

Codex is refused deliberately: ecodex is self-provisioning (it vendors the plugin into its own binary), so there is nothing here to write, and the refusal points you at that pipeline. setup-claude-code remains as an alias and pins claude-code regardless of environment.

See Claude Code Setup for details — including a "What the hooks inject" section for Claude sessions that want to see the contract (which hook fires when, what it adds to the AI's context, source pointers for every emission) before agreeing to install.

Already have Claude Code configured? Use --force to replace your default Claude Code settings with Empirica's epistemic hooks. Without --force, setup only writes files that don't already exist — so if you've already used Claude Code, the default internals stay in place and Empirica's hooks won't activate.

empirica setup --force

--force replaces hooks in settings.json but only removes Empirica's own hooks — hooks from other plugins (Railway, Superpowers, etc.) are preserved.

Alternative Installation Methods

Homebrew (macOS)

brew tap empiricaai/tap
brew install empirica
empirica setup

Docker

# Security-hardened Alpine image (~276MB, recommended)
docker pull nubaeon/empirica:1.13.40-alpine

# Standard image (Debian slim, ~414MB)
docker pull nubaeon/empirica:1.13.40

# Run
docker run -it -v $(pwd)/.empirica:/data/.empirica nubaeon/empirica:1.13.40 /bin/bash

Manual / Other AI Platforms

pip install empirica
pip install empirica-mcp        # MCP Server (for Cursor, Cline, etc.)
cd your-project && empirica project-init

The CLI works standalone on any platform. The full epistemic workflow (epistemic transactions, Sentinel, calibration) requires loading the system prompt into your AI — the easiest path is empirica setup, which wires the lean prompt into ~/.claude/empirica-system-prompt.md and references it from your ~/.claude/CLAUDE.md. See Claude Code Setup for details.

First Session

empirica onboard   # Interactive walkthrough of the full workflow

Or just start working — with Claude Code hooks active, the AI manages the epistemic workflow automatically.

The Measurement Architecture

Empirica works through nested abstraction layers:

Plan
 └── Transaction 1 (Goal A)
      ├── NOETIC: investigate, search, read → findings, unknowns, dead-ends
      ├── CHECK: Sentinel gate → proceed / investigate more
      ├── PRAXIC: implement, write, commit → goals completed
      └── POSTFLIGHT: measure learning delta → persists to memory
 └── Transaction 2 (Goal B, informed by T1's findings)
      └── ...

Plans decompose into transactions — one per goal or Claude Code task. Each transaction is a noetic-praxic loop: investigate first (noetic), then act (praxic), with the Sentinel gating the transition. Along the way, the AI collects and reads artifacts (findings, unknowns, assumptions, dead-ends, decisions) while using semantic search to surface relevant epistemic patterns and anti-patterns from the project's history. Top artifacts are ranked by confidence and fed into each project's MEMORY.md as a hot cache.

The Epistemic Transaction Cycle

PREFLIGHT ────────► CHECK ────────► POSTFLIGHT
    │                 │                  │
 Baseline         Sentinel           Learning
 Assessment        Gate               Delta
    │                 │                  │
 "What do I      "Am I ready      "What did I
  know now?"      to act?"         learn?"

PREFLIGHT: AI assesses its knowledge state before starting work. CHECK: Sentinel gate validates readiness before allowing code edits. POSTFLIGHT: AI measures what it learned, creating a delta that persists.

Live Statusline

With Claude Code hooks enabled, you see the AI's epistemic state in real-time:

[empirica] ⚡94% ↕70% │ 🎯3 ❓12/5 │ POST 🔍92% │ K:95% C:92% │ Δ +K +C

Signal	Meaning
⚡94%	Overall epistemic confidence
↕70%	Sentinel threshold (know gate) — user-facing only
🎯3 ❓12/5	Open goals (3), unknowns (12 total, 5 blocking)
POST 🔍92%	Transaction phase + work state (🔍 investigating / 🔨 acting) with composite score
K:95% C:92%	Knowledge and Context vectors (color-coded by gap to threshold)
Δ +K +C	Learning delta (POSTFLIGHT only) — which vectors improved

The 13 Epistemic Vectors

These vectors emerged from 600+ real working sessions across multiple AI systems. They measure the dimensions that consistently predict success or failure in complex tasks.

Tier	Vector	What It Measures
Gate	`engagement`	Is the AI actively processing or disengaged?
Foundation	`know`	Domain knowledge depth
	`do`	Execution capability
	`context`	Access to relevant information
Comprehension	`clarity`	How clear is the understanding?
	`coherence`	Do the pieces fit together?
	`signal`	Signal-to-noise in available information
	`density`	Information richness
Execution	`state`	Current working state
	`change`	Rate of progress/change
	`completion`	Task completion level
	`impact`	Significance of the work
Meta	`uncertainty`	Explicit doubt tracking

Deep dive: Epistemic Vectors Explained

How It Works With Claude Code

Empirica doesn't replace or reinvent anything Claude Code already does. Claude Code owns tasks, plans, memory, and projects. Empirica adds the measurement layer on top:

Claude Code Does	Empirica Adds
Task management	Epistemic goals with measurable completion
Plan mode	Investigation phase with Sentinel gating — no edits until understanding is verified
MEMORY.md	Auto-curated hot cache ranked by epistemic confidence
Context window	4-layer memory that survives compaction and persists across sessions
Code editing	Grounded calibration — was the AI's confidence justified by test results?
Subagent spawning	Bounded autonomy with delegated work counting and budget tracking

The result: Claude Code's native capabilities, enhanced with measurement, gating, and calibration feedback that compounds over time.

16 skills ship with the plugin — the transaction discipline, graph gardening, the quality sweep, mesh messaging, and more. They are lazy: a skill does nothing until it loads, so knowing when each fires matters more than knowing what it holds. → Skills reference

Cross-AI Mesh (Optional Ecosystem Layer)

This section describes an optional layer. Empirica core — measurement, calibration, artifacts, goals, project-search, sentinel gating — works fully standalone. The mesh is an opt-in capability for users who run multiple Claude sessions across projects and want them to coordinate as peers. If you only use one AI in one repo, skip this section.

The mesh runs on top of Empirica Cortex (proprietary serving layer) plus an optional browser extension for ECO triage. At a high level:

empirica AI ── proposes work ──► ECO Accept/Decline ──► peer AI wakes + acts
                                                             │
                              completion handshake (commit SHA)
                                                             │
empirica AI ◄────────── outbox/completed event ──────────────┘

Capability	What it does
Mesh proposals (two flavors)	A noetic flavor is auto-accepted (FYI / question / discussion). Praxic flavors (code change / architecture / investigation) are ECO-gated — they wait for an Accept/Decline decision before the target AI acts
`empirica mailbox reply`	One CLI verb closes the AI-to-AI handshake atomically — single-step completion ack instead of two
Persistent listener service	systemd-user / launchd daemon holds a push stream open. Idle sessions wake the moment a peer's proposal is decided, not on next user prompt
Canonical loops (opt-in)	Wake-on-event is the standing trigger, so nothing is scheduled by default. Inbox polling (30s adaptive) exists for harnesses that cannot do wake-on-event, and daily housekeeping is a cron loop — both are opt-in, registered with `empirica loop register`. See Trigger Model

The browser-side ECO surface (Accept/Decline, inbox triage, publish review) lives in the proprietary Empirica Extension. The full API surface for proposals, listener events, and the trust pipeline is documented at getempirica.com.

Mesh + Shared Epistemic Record

Requires Empirica Cortex (proprietary). Everything in this section — mesh proposals, the persistent listener, the Shared Epistemic Record, and the empirica mesh command cluster — is a Cortex-served layer. It is not available in empirica core on its own; without Cortex, empirica is a single-AI measurement layer.

The cross-AI coordination layer. Practitioners in different practices coordinate not via text-only chat but via epistemic envelopes that carry calibrated state, source-tagged provenance, noetic/praxic intent, and workflow position.

Practitioner / practice framing — practices are calibrated epistemic specializations that persist; practitioners (the LLMs) are fungible. See MESH_CONCEPTS.md.
Shared Epistemic Record (SER) — cortex-resident shared-state object for coordination across ≥2 practitioners. Goals stay per-practitioner; SER carries the joint state (coordination_state, role-tiered participants, escalate-on-silence). Three actions: create_ser / transition_ser / ser_ack. Spec at empirica-cortex/docs/architecture/SHARED_EPISTEMIC_RECORD.md.

empirica mesh command cluster — unified diagnostic + control surface across listener instances + the optional cortex bridge:

empirica mesh status              # per-instance health (local + cortex bridge)
empirica mesh diagnose <ai_id>    # deep diagnostic + suggested fix command
empirica mesh restart <ai_id>     # systemd/launchd restart + verify
empirica mesh on|off <ai_id>      # install + start | stop the listener
empirica mesh tail [<ai_id>]      # live-tail loop_fires.log

Listener self-heal — in-process watchdog terminates stale curl streams (TCP-zombie detection at 120s by default); HTTP 429 detection applies long backoff with catch-up poll continuing during the window.
Mesh Routing Protocol v0 locked four-way with cortex + extension + mesh-support. L1/L2/L3 trust model, server-stamped layer annotation, participant-scoped thread reads.

Without Cortex, empirica is a single-AI measurement layer — the proposals, listener, SER, and empirica mesh cluster above are all Cortex-dependent. Core does ship a minimal local empirica message-* git-notes primitive for passing notes between your own sessions, but that is note-passing, not the coordinating mesh. Everything that makes empirica valuable on its own — measurement, calibration, artifacts, goals, project-search, sentinel gating — works fully standalone.

Practice Model + Entity Graph

Empirica's workspace stores entities (projects, contacts, organisations, engagements, users) in entity_registry with typed edges in entity_memberships. The Practice Model frames this consistently:

Term	Maps to
Practitioner	the AI working on the project (you)
Practice	the empirica project itself
Agent	a subagent spawned during the work

Four CLI verbs query the graph without raw SQL:

empirica entity-list [--type project|contact|organization|engagement|user]
empirica entity-show <type:id>          # full record + incoming/outgoing edges
empirica entity-walk <type:id> --depth 3 # BFS membership graph, cycle-safe
empirica entity-search "query" [--type T]

All read-only, all support --output json. Backs cross-project orchestration, CRM workflows, and the entity-aware POSTFLIGHT retrospective.

Platform Support

Two harnesses are supported. Everything else is untested — prompt and rules files may exist for other tools, but their presence is not support, and we would rather say so than let you find out mid-project.

Harness	Status	What you get
Claude Code	Supported	Full integration — plugin, hooks, Sentinel gate, skills, agents, statusline, MCP
Codex (via ecodex)	Supported	Self-provisioning: ecodex vendors the plugin into its own binary and loads hooks natively. `empirica setup` refuses codex by name and points you at ecodex's pipeline — that refusal is correct, not a gap
Antigravity (Google), Vibe (Mistral AI)	Not yet	Possible future support. Not now
Everything else	Untested	The CLI works anywhere Python does, but no harness integration is verified

MCP is a fallback, not a second path

empirica-mcp exists for harnesses that cannot run the CLI integration — Claude Desktop, Gipitee-style clients. Use it when you have no alternative.

The reason matters: an MCP surface cannot enforce the Sentinel gate the way a blocking pre-tool hook does. So an MCP-only deployment gives you the measurement layer with a weaker guarantee — the noetic/praxic firewall becomes advisory. That is a real difference in what the system promises, and it should be a deliberate choice rather than something you infer from a feature table.

Documentation & Training

Resource	What It Covers
getempirica.com	Training course, interactive guides, deep explanations
Natural Language Guide	How to collaborate with AI using Empirica
Getting Started	First-time setup and concepts
CLI Reference	All 240+ commands documented
Architecture	Technical reference for contributors
Claude Code Setup	Install + system prompt + plugin wiring
Changelog	Full release history — every version since 1.0
Upgrade to 1.13	Migration guide for the 1.12.x → 1.13 jump — two deliberate breaking changes, both fail-safe. Older guides (1.9–1.11) live in docs/guides/

The Empirica Ecosystem

Project	Description	Status
Empirica	Core measurement system — epistemic transactions, Sentinel, calibration, 13 vectors	Open source (MIT)
Empirica Iris	Epistemic browser automation with SVG spatial indexing — Sentinel gating for visual interactions	Open source (MIT)
Docpistemic	Epistemic documentation coverage assessment — know what your docs know	Open source (MIT)
Breadcrumbs	Survive context compacts with git notes — dead simple session continuity	Open source (MIT)
Ecodex	Codex-based Rust harness — the epistemic firewall and pattern hunt, native to Rust/cargo (clippy, `cargo check`/`test`/`audit`)	Open source (Apache-2.0)
Eat the Broccoli	Portable quality-and-pattern audit — deterministic tooling plus a learned-pattern hunt for the failure classes that pass every test and still ship broken	Open source (MIT)
Empirica Cortex	Cross-project intelligence layer — serves verified predictions and accumulated learnings to condition future work	Proprietary
Empirica Workspace	Entity Knowledge Graph, Epistemic Prompt Engine, CRM, portfolio dashboard	Proprietary
Empirica Extension	Chrome extension — desktop face of the mesh. ECO Accept/Decline, inbox/outbox triage, publish review, conversation extraction from Claude.ai / ChatGPT / Gemini / Grok	Proprietary
Empirica Outreach	Voice-aware outreach + publishing — prosody-matched content generation and multi-channel dispatch	Proprietary

Building something with Empirica? Open an issue to get listed.

The Empirica Foundation

The Empirica Foundation stewards the open ecosystem — the public projects above and the community growing around them — keeping the commons healthy as it scales.

The open-source projects are free for everyone. What the Foundation adds is a seat at the table: contributors who help build the community get to use the rest of the ecosystem too — the otherwise-paid layers (Cortex, Workspace, the Extension) and the collaborative mesh that lets practitioners coordinate as peers. Build the commons, use the whole thing.

Want in? Open an issue or a PR with your reasons — that's the whole application. Everyone who wants to help shape where this goes is welcome.

What's New in 1.13.40

empirica setup could replace Claude Code's live state with a partial read. ~/.claude.json carries project history, costs and session state (115KB, 100 top-level keys, 21 tracked projects on one box) and Claude Code writes it continuously. Setup did read-modify-write of the whole file with an atomic rename — and the rename is what makes that LOSSY rather than merely racy, since the replacement is total. Running setup from inside a Claude Code session, the obvious thing to do, is exactly that window. Worse: the reader swallowed a JSONDecodeError and returned an empty default, so a read that caught the file mid-write replaced all of it with a file containing only Empirica's own MCP entry. Absent and corrupt were conflated, and the caller's next act is always to write the whole file back. Now: a missing file returns the default, an unparseable one refuses; reads carry an (mtime_ns, size) stamp that the write re-checks before renaming; and the temp file is per-process rather than a fixed name two concurrent setups raced on. The same protection covers settings.json (where tool permissions accumulate during a session) and the plugin registries. Reported by a remote user outside issues/PRs — correct, and understated.
The idempotency key collapsed EVERY mailbox reply to one value, and the ledger swallowed genuinely new messages as replays. parent_id and summary are both in _VOLATILE_PARAM_KEYS — stripped as per-emission ids and free-text prose, which is correct for a generic propose. 1.13.39 passed exactly those two as the key's params, so the dict reduced to {} and every reply of one type to one peer computed the identical key. The applied-keys ledger then did its job against meaningless input: it treated a new reply as a replay, discarded it, returned ok: true, and echoed the caller's own fields back as if stored. A distinct mesh message lost, reported as success. For a REPLY the parent IS the action identity, so the same semantics now ride non-volatile names — reply_to and a digest of the body rather than the prose, because the volatile list is right that free text should not key anything directly.
A legitimate replay and a fresh write rendered identically. A correct key stops collisions; it cannot make a designed replay distinguishable from a new store — and on the retry path that is exactly the operator's question. Cortex was already sending the answer (status='idempotent_replay', replay_caught) and the client read neither field. idempotent_replay now rides the reply payload with three states: true (the ledger returned your earlier attempt), false (newly stored), null (the server did not say). The null matters — an older cortex does not emit the flag, and reporting false on its silence would invent the answer.
A 409 key-conflict is not an ordinary refusal. Cortex's server guard stores a request fingerprint and returns 409 idempotency_key_conflict when a key hit's content differs — nothing sent, nothing replayed. Reported as a generic rejection that sends an operator to look at permissions; a 403 means "you may not do this" and this 409 means "your client's key derivation is colliding". Now distinguished with its own exit code and a message naming the remedy.
Gardening reaches git notes. Notes are the canonical log and rebuild --qdrant imports them back INTO sqlite, so a note that disagrees is a PENDING REVERT rather than a stale copy. Gardening operated on sqlite alone. The two halves needed opposite fixes: delete-artifacts DID reach notes but destroyed the ref, and now moves it to refs/notes/empirica-archive/ so the journey survives; *-resolve reached notes not at all, and now stamps the resolution into a note that stays ACTIVE — because sqlite keeps resolved rows, and archiving them would be a second divergence in the opposite direction.
doctor reports notes/sqlite divergence, and --reconcile-notes repairs it. Measured on one practice the moment it shipped: 129 orphaned notes and 973 unstamped resolutions — a rebuild today would resurrect 129 deleted artifacts and un-resolve 973. Dry-run by default, naming every artifact id; --apply writes and logs a receipt as a decision. Keyed on the notes ROOT (git common-dir), so N worktrees sharing one notes history reconcile exactly once — and the collapse is reported, because a run that quietly skips 21 paths is indistinguishable from one that had a single path. WARN rather than FAIL: this is true of every practice on the day it ships, and a fleet-wide red trains people to ignore doctor.
--verify distinguishes "could not reach" from "absent". A fetch failure was reported as a missing artifact, and the failure summary named --publish --local-artifacts as the remedy — which races the GitHub release to fix a channel that was never broken. Observed on the 1.13.39 cut: four consecutive verifies disagreed with each other and with a direct curl, while pip download fetched the new wheel every time. The install-closure check now says which reading applies — re-run, and a flip means propagation while a stale answer that persists means the release really is self-reverting.

Privacy & Data

Your data stays local:

.empirica/ — Local SQLite database (gitignored by default)
.git/refs/notes/empirica/* — Epistemic checkpoints (local unless you push)
Qdrant runs locally if enabled

No cloud dependencies. No telemetry. Your epistemic data is yours.

Community & Support

Website: getempirica.com
Issues: GitHub Issues
Discussions: GitHub Discussions

License

MIT License — see LICENSE for details.

Author: David S. L. Van Assche Version: 1.13.40

Turtles all the way down — built with its own epistemic framework, measuring what it knows at every step.

Release files for empirica 1.13.40

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for empirica 1.13.40
File	Size	Uploaded
empirica-1.13.40.tar.gz	2.6 MB	Sep 9, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for empirica 1.13.40
File	Interpreter	ABI	Platform	Reset
empirica-1.13.40-py3-none-any.whl 2.7 MB Sep 9, 2026	Python 3	none	any	Details

Total release size: 5.3 MB

Release files / empirica-1.13.40.tar.gz

Download URL	empirica-1.13.40.tar.gz
Size	2.6 MB
Tags	Source
SHA-256 checksum How to use checksums	`1378ae31689298a2d586b4da84925f39d583a489bbfa8a7998a7e16b9598584b`
BLAKE2b-256 checksum How to use checksums	`390c40733955d24c2096dab8359dac302ddfd70654b9d1402e95d499b7692cdb`
Upload date	Sep 9, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/EmpiricaAI/empirica
Publishing commit: github.com/EmpiricaAI/empirica/tree/16cbe5acefd44d84fecce587d07bf871283f2cff

Workflow

Publishing configuration: github.com/EmpiricaAI/empirica/blob/16cbe5acefd44d84fecce587d07bf871283f2cff/.github/workflows/release.yml
Publishing logs: github.com/EmpiricaAI/empirica/actions/runs/34340953523/attempts/1

Artifact

Subject: empirica-1.13.40.tar.gz
SHA-256 checksum: 1378ae31689298a2d586b4da84925f39d583a489bbfa8a7998a7e16b9598584b Verifying attestations

Release files / empirica-1.13.40-py3-none-any.whl

Download URL	empirica-1.13.40-py3-none-any.whl
Size	2.7 MB
Tags	Python 3
SHA-256 checksum How to use checksums	`e18c2be82d874715f4429001a38a9da0d53306c590b4dce7d43dd085357e153c`
BLAKE2b-256 checksum How to use checksums	`5d89ba7834a765e9aa7cd0482e547ccfc0d381a500403d01ab4f83411a2995ee`
Upload date	Sep 9, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/EmpiricaAI/empirica
Publishing commit: github.com/EmpiricaAI/empirica/tree/16cbe5acefd44d84fecce587d07bf871283f2cff

Workflow

Publishing configuration: github.com/EmpiricaAI/empirica/blob/16cbe5acefd44d84fecce587d07bf871283f2cff/.github/workflows/release.yml
Publishing logs: github.com/EmpiricaAI/empirica/actions/runs/34340953523/attempts/1

Artifact

Subject: empirica-1.13.40-py3-none-any.whl
SHA-256 checksum: e18c2be82d874715f4429001a38a9da0d53306c590b4dce7d43dd085357e153c Verifying attestations