Create the os-me Store repository and its charter #939

Closed
opened 2026-10-04 20:15:17 +00:00 by jared · 3 comments
Owner

Problem

The os-me skill cannot learn without a place to store and evolve its knowledge.

Question

Where is the Store, and what is the least text it needs to start and to change itself?

Context

Map: #936

  • Create a private repository on Forgejo (jared/os-me-store), cloned at ~/dev/os-me-store. Use /git-context:repo-init.
  • Seed one charter file. It holds: the goal (predict and give Jared's response; success is that he types less), the guardrails from the map, the freedom rule (the skill owns all other content and structure, including its entry file), the quality rule (small, high-quality, remove stale material), and the cost rule (record token use per run; reduce it as accuracy becomes stable).
  • Seed one suggestions file. Each entry is a suggestion from Jared, not a rule. First entries: (1) his three most frequent corrections: challenge the problem more deeply; do not let a rule or an ADR block a better design; give the critic an independent view. (2) The procedure "first assume I disagree, then use what is known about me to find out why". (3) Ask why he would make a correction and what that says about how he frames problems. (4) Know when an answer is good enough: past the point of small returns, stop and move on. (5) The takedown round 4 run of 2026-10-04 used three reads: blind root cause, audit of the AI's own claims, prediction.
  • Do not design the Store's structure. The kickoff run does that.

AFK.

## Problem The os-me skill cannot learn without a place to store and evolve its knowledge. ## Question Where is the Store, and what is the least text it needs to start and to change itself? ## Context Map: #936 - Create a private repository on Forgejo (`jared/os-me-store`), cloned at `~/dev/os-me-store`. Use `/git-context:repo-init`. - Seed one charter file. It holds: the goal (predict and give Jared's response; success is that he types less), the guardrails from the map, the freedom rule (the skill owns all other content and structure, including its entry file), the quality rule (small, high-quality, remove stale material), and the cost rule (record token use per run; reduce it as accuracy becomes stable). - Seed one suggestions file. Each entry is a suggestion from Jared, not a rule. First entries: (1) his three most frequent corrections: challenge the problem more deeply; do not let a rule or an ADR block a better design; give the critic an independent view. (2) The procedure "first assume I disagree, then use what is known about me to find out why". (3) Ask why he would make a correction and what that says about how he frames problems. (4) Know when an answer is good enough: past the point of small returns, stop and move on. (5) The takedown round 4 run of 2026-10-04 used three reads: blind root cause, audit of the AI's own claims, prediction. - Do not design the Store's structure. The kickoff run does that. AFK.
Author
Owner

Start: creating private repo os-me-store and seeding charter files.

Start: creating private repo os-me-store and seeding charter files.
Author
Owner

Done: private repo jared/os-me-store at ~/dev/os-me-store, seeded CHARTER.md, SUGGESTIONS.md, ENTRY.md, queue/.gitkeep; pushed.

Done: private repo jared/os-me-store at ~/dev/os-me-store, seeded CHARTER.md, SUGGESTIONS.md, ENTRY.md, queue/.gitkeep; pushed.
Author
Owner

Resolution

Done: Private Store repository created at ~/dev/os-me-store with remote jared/os-me-store; seeded with CHARTER.md, SUGGESTIONS.md, ENTRY.md, queue/.

Evidence: Store commit 956bad9 pushed to origin main; unauthenticated request to the repository URL returned 404.

Follow-ups: none

## Resolution **Done:** Private Store repository created at ~/dev/os-me-store with remote jared/os-me-store; seeded with CHARTER.md, SUGGESTIONS.md, ENTRY.md, queue/. **Evidence:** Store commit 956bad9 pushed to origin main; unauthenticated request to the repository URL returned 404. **Follow-ups:** none
jared closed this issue 2026-10-04 20:59:22 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jared/cc-os#939
No description provided.