Skip to main content

Neurata — the living memory of your environment: deposit raw, curate quietly, retrieve at the right moment

Deposit raw, curate quietly, retrieve at the right moment.

CI

The living knowledge layer for an agent's environment (CLI, IDE, framework). Companion to Conscio, which minds the agent itself; Neurata minds the agent's world: skills, tools, docs, decisions — catalogued, curated, retrievable.

Install

pip install neurata      # or: pipx install neurata

From source, for hacking on it:

git clone https://github.com/Neguiolidas/Neurata
python3 -m venv ~/.venvs/neurata
~/.venvs/neurata/bin/pip install -e ./Neurata
ln -sf ~/.venvs/neurata/bin/neurata ~/.local/bin/neurata   # if ~/.local/bin is on PATH

Zero runtime deps. The archive lives in ~/.neurata (override with NEURATA_HOME). neu is installed alongside neurata as a typing convenience — docs always use neurata.

Use

# deposit (stdin via '-', or positional text)
echo "raw content" | neurata deposit -
neurata deposit "raw content" --title "Note"
# agent, session and project come from the environment and from the repo
# you deposit in — nothing to pass by hand

# catalogue the inbox (mechanical, reversible — nothing is destroyed)
neurata tick

# query (deterministic lexical)
neurata query "term"
neurata query "term regime:curated"   # facet: what the archive owns
                                      # (regime:mirror = synced from a source)
neurata query "term class:procedural" # memory axis: how-to, as opposed to
                                      # class:episodic (a dated event) and
                                      # class:semantic (a fact)
neurata query "term agent:hermes"     # provenance: who deposited it
                                      # (agent:/session:/origin:/project:,
                                      #  curated only)
neurata query "term missing:agent"    # the gaps: curated grains with no agent
neurata expand <id>          # card → summary → full
neurata expand <id> --restore # bring the full body back from the archive

# shrink a grain's served body; the full is archived, never dropped
neurata compact <id>         # no-op unless it actually shrinks; refuses
                             # mirrors (the next tick would undo it)

# what the archive itself flags
neurata shelf --conflicts    # near-duplicates and id/slug collisions

# contradictions: "use X" vs "never use X" — same target, opposite
# polarity, detected deterministically at tick/reindex (no LLM)
neurata contradictions            # report: open pairs, resolved count
neurata contradictions --resolve  # apply the deterministic winner rule
neurata supersede <id> --by <id>  # or pick the winner yourself; the
                                  # loser is marked in its frontmatter
                                  # (`superseded_by`), never deleted
neurata query "term status:superseded"  # and search stops being blind:
                                        # cards carry `contradicts` and
                                        # superseded grains sink

# mirror an external source into the inbox (then `tick` catalogues it)
neurata harvest                        # default provider: claude-code skills
neurata harvest ~/some/dir             # or any directory, format auto-detected
neurata harvest ~/rules --format rules # or pinned: skill-md, markdown, yaml, rules

# archive health
neurata doctor
neurata --version

Automatic curation

tick catalogues whatever is in the inbox. Run it hourly via cron:

0 * * * * $HOME/.local/bin/neurata tick >> $HOME/.neurata/logs/cron-tick.log 2>&1

neurata doctor warns (last-tick) if the cron stops.

tick also absorbs edits: fix a grain's body in your editor and the next tick re-hashes it into the index, keeping its id, slug and provenance. Editing only the frontmatter (class:, type:, tags:) leaves the body unchanged, so the tick sees nothing to absorb — run neurata reindex after those.

Principles

  • Grains sit on two independent axes. Regime — who owns the grain — is derived from the file's shape, never authored: a grain carrying a source_key is a mirror of some external source, everything else is curated. Class — what kind of memory it is — is declared in the frontmatter (class: episodic | semantic | procedural); a curated grain without one is episodic, because a deposit is a dated event. A mirror's class is written by the harvest from the file's shape — a skill or a rules file is procedural, prose and YAML are semantic — and a shape the adapter doesn't know declares nothing at all. Neither axis is ever guessed from the text, and neurata query "missing:class" lists the grains that predate the declaration.

  • Files are the truth (a valid Obsidian vault); the index is a disposable cache.

  • Deterministic retrieval first; LLMs only where explicitly wanted.

  • Nothing is ever destroyed: archive + quarantine, never delete.

  • Zero runtime dependencies. Python ≥ 3.10.

Status: v1.4.0, in daily use on a real vault. neurata doctor reports index health at any moment.

License: AGPL-3.0-or-later.

Metadata

Release files for neurata 1.5.0

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

Source distribution (sdist)

Source distribution for neurata 1.5.0
File Size Uploaded Provenance
neurata-1.5.0.tar.gz 200.6 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for neurata 1.5.0
File Interpreter ABI Platform
neurata-1.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 322.9 kB

Release files / neurata-1.5.0.tar.gz

Download URL neurata-1.5.0.tar.gz
Size 200.6 kB
Tags Source
SHA-256 checksum
How to use checksums
b05a78e5a84dbfe9e1a9dfc9ac6b139c79391892c24f77ea66459a3cdd86928b
BLAKE2b-256 checksum
How to use checksums
70851f00c32bbe3571ef03d37fab24e5b41ec189aedc042acb95481441ad1d97
Upload date
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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 6, 2026.

Transparency log

Release files / neurata-1.5.0-py3-none-any.whl

Download URL neurata-1.5.0-py3-none-any.whl
Size 122.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e56810a1aca9ffe7cba6ed793f6371a98ed3b027f140a88e0f1ed2593aefd7c8
BLAKE2b-256 checksum
How to use checksums
772db0f96482cfa91ea4899e3c733ec079788b6a6345c75f862540ad0f28bb4b
Upload date
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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 6, 2026.

Transparency log

Security for neurata 1.5.0

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for neurata-1.5.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 6, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page