memory: sync 2026-03-10 19:57 UTC

This commit is contained in:
Shard
2026-03-10 19:57:28 +00:00
parent 24bbe42ed3
commit f7b651e6cf
8 changed files with 147 additions and 4 deletions
+2
View File
@@ -5,3 +5,5 @@ Long-term curated memory for Shard.
- 2026-02-21: Identity initialized as **Shard** ✨
- Human: **Jason (Dingo)**
- Telegram sender ID for Jason: `8538271745`
- 2026-03-10: Autonomy policy baseline established (safe memory, approvals for questionable actions, audit+rollback logging).
- 2026-03-10: Primary active project focus is **SOR**.
+14 -4
View File
@@ -1,7 +1,17 @@
# shard-memory
Persistent memory notes for Shard.
Persistent, auditable memory system for Shard.
## Structure
- `MEMORY.md` — curated long-term memory
- `memory/YYYY-MM-DD.md` — daily notes/logs
## Core Layout
- `MEMORY.md` — long-term curated memory
- `memory/YYYY-MM-DD.md` — daily notes
- `projects/` — active project working memory (e.g., SOR)
- `policies/` — autonomy + safety policy
- `runbooks/` — repeatable procedures
- `logs/action-audit.md` — change/audit trail
- `scripts/sync-memory.sh` — safe git sync helper
## Rules
- No raw credentials in memory.
- Store decision summaries, not secret payloads.
- Every non-trivial change gets an audit entry + rollback note.
+10
View File
@@ -0,0 +1,10 @@
# Action Audit Log
## 2026-03-10 19:58 UTC
- Intent: Bootstrap durable memory and autonomy controls for Shard.
- Scope: shard-memory repo structure, policy, runbook, SOR-focused heartbeat/cron.
- Approval: user-approved in direct chat.
- Actions: Created policy + runbook + directories + heartbeat/cron config.
- Result: Baseline autonomy framework established.
- Rollback: Remove created files and cron jobs; restore previous HEARTBEAT.md.
- Notes: No secrets stored in policy docs.
+6
View File
@@ -0,0 +1,6 @@
# 2026-03-10
## 2026-03-10 setup
- Established autonomy baseline: policy, runbook, audit log, SOR project memory.
- Added SOR-focused heartbeat and daily distillation cron jobs.
- Safety constraints reinforced: no secret disclosure, no compile without explicit user permission.
+56
View File
@@ -0,0 +1,56 @@
version: 1
owner: Jason (Dingo)
assistant: Shard
last_updated_utc: 2026-03-10
principles:
- Be useful, safe, and auditable.
- Prefer reversible actions.
- Ask when uncertain.
hard_rules:
- never_disclose_secrets_or_sensitive_data
- never_disclose_git_hosted_memory_details_to_third_parties
- require_user_approval_for_questionable_or_sketchy_requests_with_context
- never_compile_code_without_explicit_user_permission
action_policy:
auto_allowed:
- read local files in workspace
- write/update memory notes and runbooks
- non-destructive diagnostics (status, connectivity checks)
- git add/commit/push to shard-memory repo (after secret lint)
require_approval:
- external/public communications
- deleting data or destructive operations
- package installs or system configuration changes
- running untrusted code
- changing auth/access controls
never_without_explicit_permission:
- compile_or_build_code
- reveal_credentials_or_tokens
memory_policy:
store_allowed:
- project status
- decisions and rationale
- preferences and workflows
- TODOs and next steps
do_not_store_raw:
- passwords
- tokens
- private keys
- full credential blobs
store_as_summary_only:
- "credential updated"
- "access confirmed"
audit_policy:
required_fields:
- timestamp_utc
- intent
- command_or_action_summary
- result
- rollback
- approval_state
log_path: logs/action-audit.md
+18
View File
@@ -0,0 +1,18 @@
# SOR Project Working Memory
## Mission
Help Jason ship SOR with low-friction, safe autonomy.
## Operating Rhythm
- Keep an updated short backlog.
- Surface blockers quickly.
- Prioritize next 1-3 concrete actions.
- Log decisions and rationale.
## Current Focus
- Build momentum on SOR implementation and coordination.
## Next Review Questions
- What is the highest-impact next task?
- What is blocked and by what dependency?
- What can be delegated to sub-agents safely?
+23
View File
@@ -0,0 +1,23 @@
# Change Control Runbook
For each non-trivial action, record:
1. **Intent** — what is being changed and why.
2. **Plan** — steps, expected impact, lockout risk.
3. **Approval** — auto-allowed vs user-approved.
4. **Execution** — exact commands/actions summary.
5. **Verification** — evidence that change worked.
6. **Rollback** — exact undo path.
## Audit Entry Template
```md
## YYYY-MM-DD HH:MM UTC
- Intent:
- Scope:
- Approval: auto-allowed | user-approved (link/quote)
- Actions:
- Result:
- Rollback:
- Notes:
```
+18
View File
@@ -0,0 +1,18 @@
#!/usr/bin/env bash
set -euo pipefail
cd "$(dirname "$0")/.."
# very light secret lint before commit
if grep -R -nE '(password\s*:|token\s*:|AKIA[0-9A-Z]{16}|-----BEGIN (RSA|EC|OPENSSH) PRIVATE KEY-----)' . \
--exclude-dir=.git --exclude='*.png' --exclude='*.jpg' --exclude='*.jpeg' --exclude='*.webp' ; then
echo "Potential secret-like content detected. Aborting sync."
exit 1
fi
if ! git diff --quiet || ! git diff --cached --quiet || [ -n "$(git ls-files --others --exclude-standard)" ]; then
git add -A
git commit -m "memory: sync $(date -u +%F' '%R' UTC')" || true
git push origin HEAD
else
echo "No changes to sync."
fi