klyd
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░ ░░░░ ░░░ ░░░ ░░░ ░░░ ░░░░ ░░ ░░░░░░░░ ░░░░░░░░ ░░░░ ░
▒ ▒ ▒ ▒▒ ▒▒▒▒ ▒▒▒▒▒ ▒▒▒▒▒ ▒▒▒▒ ▒▒ ▒▒▒▒ ▒▒ ▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒ ▒▒ ▒
▓ ▓▓ ▓▓▓▓ ▓▓▓▓▓ ▓▓▓▓▓ ▓▓▓▓▓▓▓▓ ▓▓ ▓▓▓▓▓▓▓▓ ▓▓▓▓▓▓▓▓ ▓
█ ██ ██ █████ █████ ████ ██ ████ ██ ████████ ████████ █ █ █
█ ████ ██ ████ █████ ██████ ███ ████ ██ ██ ██ ████ █
████████████████████████████████████████████████████████████████████████████████
Persistent architectural memory for autonomous coding agents.
Current status
Early design & specification phase. Subsystem boundary defined; codebase scaffolded.
Overview
Large Language Models (LLMs) tend to lose architectural context and make regression decisions over long coding sessions. klyd solves this by acting as a persistent architectural memory layer. It extracts architectural decisions from git history/diffs, stores them locally, and retrieves relevant constraints at write time to keep autonomous agents aligned with project guidelines.
klyd remembers. The kernel enforces.
Core Features
- Architectural Decision Extraction: Auto-extracts design constraints and guidelines from repository changes and commit history.
- Local Memory Store: Uses a lightweight local SQLite database to persist constraints offline.
- Context Retrieval: Queries relevant architectural constraints based on the files currently being edited.
- Agent Prompt Injection: Injects retrieved guidelines into agent execution loops to guide code generation.
Relationship to Kernel
- klyd (Memory): Tracks and provides the historical context and architectural rules.
- Kernel (Enforcement): Deteministically evaluates code changes at the write-path to ensure those rules are not violated.
Non-goals
- Write-path interception:
klyddoes not block files or handle save hooks; that is the sole responsibility of the Kernel. - Code Generation:
klyddoes not generate or rewrite source code.
Installation
pip install -e .
Usage
klyd --help
python -m klyd --help
Links
Metadata
Release files for watchllm-klyd 0.1.1
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 | |
|---|---|---|---|---|
| watchllm_klyd-0.1.1.tar.gz | 17.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| watchllm_klyd-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 31.4 kB
Release files / watchllm_klyd-0.1.1.tar.gz
| Download URL | watchllm_klyd-0.1.1.tar.gz |
|---|---|
| Size | 17.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
479fdf5287ed0cccd0ec9fde12b4835a2bf36a25a9703b552b64079d6c029afc
|
|
BLAKE2b-256 checksum How to use checksums |
ead8080934023c7f05c189daa46429a4c4487896e9e769636af13614bebfa8d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Release files / watchllm_klyd-0.1.1-py3-none-any.whl
| Download URL | watchllm_klyd-0.1.1-py3-none-any.whl |
|---|---|
| Size | 13.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
585198977bdd8578ec06f7c9c0b0f6dbc2d447f844fb6c2722f91d156999f7bd
|
|
BLAKE2b-256 checksum How to use checksums |
a03208640431c135411cb76279f391274ca647a0f4a6201669c3ccc0102aac52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Security for watchllm-klyd 0.1.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.