Skip to main content

Braingent Memory Repo

This is a Markdown-first engineering memory repository based on Braingent, created by JJ Adonis.

Use it as a durable memory layer for AI-assisted software engineering work. Claude, Codex, ChatGPT, and other tools should read this repo before planning meaningful work and should capture important outcomes after the work is done.

What Goes Here

  • Project and repository profiles.
  • Task records.
  • Code review records.
  • Decision records.
  • Reusable learnings.
  • Tool and version notes.
  • Ticket stubs for cross-cutting work.
  • Optional live BGT-NNNN agent tasks for active coordination.
  • Optional dashboard docs for a read-only live task UI.
  • An installable braingent helper CLI for search, validation, reindexing, task files, MCP retrieval, and QA generation.
  • The packaged QA generator for Markdown, Xray JSON, TestRail CSV, and Gherkin outputs.
  • Raw imports before they are summarized.
  • Preferences that guide future AI agents.

Read First

Agents should start here:

  1. AGENTS.md or CLAUDE.md, depending on the tool.
  2. INDEX.md.
  3. CURRENT_STATE.md.
  4. preferences/.
  5. tasks/INDEX.md if live tasks are enabled and the work may already be active.
  6. Relevant organization, project, repository, topic, tool, ticket, or person records.

Core Workflow

Before work:

  • Read the root instructions.
  • Search memory for relevant context.
  • Check live tasks before creating overlapping active work.
  • Reuse prior decisions and conventions.

During work:

  • Track decisions, versions, commands, failures, fixes, tickets, PRs, branches, and follow-ups.
  • Append activity to a live BGT-NNNN task when coordination or handoff matters.

After work:

  • Create or update a durable record.
  • Link completed live tasks to durable records with agent_task: BGT-NNNN.
  • Update indexes or current state if needed.
  • Commit the memory change.

Start with free-text search:

rg -n "<query>" .

Use the packaged structured search helper:

braingent find kind=decision
braingent recall repo=repo--example--owner--repo

You can also search frontmatter fields directly:

  • record_kind
  • status
  • organization
  • project
  • repositories
  • ticket
  • topics
  • tools
  • people
  • ai_tools

Safety

Never store secrets, credentials, tokens, private keys, customer secrets, or sensitive personal data in this repo.

Use placeholders and links instead of copying sensitive evidence.

Release files for braingent 1.0.1

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

Source distribution (sdist)

Source distribution for braingent 1.0.1
File Size Uploaded
braingent-1.0.1.tar.gz 111.5 kB Details

Built distribution (wheel)

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

Total release size: 269.5 kB

Release files / braingent-1.0.1.tar.gz

Download URL braingent-1.0.1.tar.gz
Size 111.5 kB
Tags Source
SHA-256 checksum
How to use checksums
f2d23bf71d03af48bbcd94bbc56f5e0232900c3a40303cbb7a742984fa228fd3
BLAKE2b-256 checksum
How to use checksums
0ad95ca5e2d14a63474ca7160dbd1efc3ad11c3d19cac03ac2700db49f830688
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 17, 2026.

Transparency log

Release files / braingent-1.0.1-py3-none-any.whl

Download URL braingent-1.0.1-py3-none-any.whl
Size 158.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c7700656c79e7079c07038d991ac4e2f82dfd16556870f3454efe3c7c0e8f056
BLAKE2b-256 checksum
How to use checksums
7f208711abad54b703fcd28c066821541fe3f2feb17b671e15db1097cfd33340
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 17, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.1 This release

2 release files

1.0.0

2 release files

0.1.1

2 release files

0.1.0

2 release files

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