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.
- Epic pages that group work across tickets and repositories, with a config-to-enable ledger.
- Optional live
BGT-NNNNagent tasks for active coordination. - Optional dashboard docs for a read-only live task UI.
- An installable
braingenthelper 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:
AGENTS.mdorCLAUDE.md, depending on the tool.INDEX.md.CURRENT_STATE.md.preferences/.tasks/INDEX.mdif live tasks are enabled and the work may already be active.- 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-NNNNtask 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.
Search
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
braingent find --epic <slug>
You can also search frontmatter fields directly:
record_kindstatusorganizationprojectrepositoriestickettopicstoolspeopleai_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.
Metadata
Release files for braingent 1.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| braingent-1.4.0.tar.gz | 137.4 kB | With provenance | Details for braingent-1.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| braingent-1.4.0-py3-none-any.whl | Python 3 | none | any | Details for braingent-1.4.0-py3-none-any.whl |
Total release size: 327.0 kB
Release files / braingent-1.4.0.tar.gz
| Download URL | braingent-1.4.0.tar.gz |
|---|---|
| Size | 137.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d742b3a378cba06d09444ac8903aef9b74e98ddd3b95564dcfe3f31afdc2c691
|
|
BLAKE2b-256 checksum How to use checksums |
4225e74d7c1b8c7de77a92ca65d31fef2c9740926077acacf65b1a134665045c
|
| 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 Oct 28, 2026.
Transparency logRelease files / braingent-1.4.0-py3-none-any.whl
| Download URL | braingent-1.4.0-py3-none-any.whl |
|---|---|
| Size | 189.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5354d0e9f6ed194900c4f109992593fb58f41c9d1e08633a573da1c03f39dee4
|
|
BLAKE2b-256 checksum How to use checksums |
be9d640a8c8998187ad33f341f4e37b7ff38ee01cc3c9d21f553ef09489cf5c3
|
| 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 Oct 28, 2026.
Transparency logSecurity for braingent 1.4.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.
Attestation for braingent-1.4.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 Oct 28, 2026.
Transparency logA 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.