Skip to content

Explain LabNote’s continuity and audit boundaries - #31

Merged
Wonderforge-Lab merged 3 commits into
mainfrom
visibility-why-labnote
Sep 7, 2026
Merged

Explain LabNote’s continuity and audit boundaries#31
Wonderforge-Lab merged 3 commits into
mainfrom
visibility-why-labnote

Conversation

@Wonderforge-Lab

Copy link
Copy Markdown
Owner

Phase 2: explain the distinction

Expands WHY_LABNOTE.md in English and Simplified Chinese.

It now separates:

  • model context from selected project continuity;
  • automatic agent memory from a visible, human-controlled project record;
  • repository context files from a route through ongoing work; and
  • runtime observability from a project-level audit trail.

It also makes the boundary around LabNote’s rails explicit: they make coordination legible and reviewable; they do not make a model deterministic or infallible.

No workflow, schema or runtime behaviour changes.

@Wonderforge-Lab
Wonderforge-Lab merged commit 677840a into main Sep 7, 2026
2 checks passed
@Wonderforge-Lab
Wonderforge-Lab deleted the visibility-why-labnote branch September 7, 2026 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant