Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
MIT License

Copyright (c) 2026 Jay / Fienna Liang

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -419,4 +419,4 @@ See [Development and contributing](docs/guides/development.md) for the fuller co

## License

MIT
Heddle is licensed under the MIT License. See [LICENSE](LICENSE).
9 changes: 7 additions & 2 deletions docs/agent-context.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,12 @@ When additional project context is needed, read in this order:
2. `../heddle-workspace-notes/agent-memory/current-state/project-summary.md`
3. This repo's live docs and code for the relevant capability area
4. the relevant focused file under `../heddle-workspace-notes/agent-memory/current-state/`
5. `../heddle-workspace-notes/agent-memory/project-context.md` only when broader long-form context is needed
6. `../heddle-workspace-notes/analysis/` and `../heddle-workspace-notes/task-plans/` as supporting historical context only
5. `../heddle-workspace-notes/agent-memory/workflows/feature-prd-to-technical-plan.md`
when the user asks for a broad feature, substantial refactor, PRD,
architecture direction, roadmap, technical plan, milestone plan, or
implementation/review workflow
6. `../heddle-workspace-notes/agent-memory/project-context.md` only when broader long-form context is needed
7. `../heddle-workspace-notes/analysis/` and `../heddle-workspace-notes/task-plans/` as supporting historical context only

For first-run situation awareness, do not stop after reading high-level memory summaries. Before answering capability-depth questions such as "what is this project?", "how does Heddle work?", or "what can it really do?", inspect the implementation path named by `agent-memory/README.md` and `current-state/project-summary.md`. The sibling notes explain intent and current state; the live code is the source of truth for actual capability depth.

Expand Down Expand Up @@ -55,6 +59,7 @@ For first-run situation awareness, do not stop after reading high-level memory s
- Prefer `docs/agent-context.md` for stable shared workflow instructions inside this repo.
- Prefer `../heddle-workspace-notes/agent-memory/` for evolving cross-session memory, project-state notes, and reminders primarily meant for future agents rather than end users.
- Prefer focused files under `../heddle-workspace-notes/agent-memory/current-state/` for active workstream handoff notes instead of putting every update only into `project-context.md`.
- Use `../heddle-workspace-notes/agent-memory/workflows/feature-prd-to-technical-plan.md` for broad feature/refactor planning and for the worker/reviewer loop after a technical plan exists.
- When the user asks to "note this down" or preserve working context, update the most appropriate file in `../heddle-workspace-notes/agent-memory/` unless the information is better treated as stable repo guidance in this repo.
- After meaningful implementation progress, update the relevant task plan, the focused `current-state/` file if one exists, and `../heddle-workspace-notes/agent-memory/project-context.md` if the broader project summary changed.
- Keep agent-memory entries concrete: current repo state, what changed, what remains, verification status, and the next recommended step.
Expand Down
Loading