alignment_status: confirmed
Social Ledger and Public Archive Decisions
This page records the approved and implemented decisions for a cross-project social post system of record, public-safe gBrain alignment links, and channel-specific reply-chain patterns for build-in-public posts.
approval_status: ready-for-agent-review and consumed on 2026-06-26. The approved conventions, package assets, generated alignment guidance, and tests are written. This page is current for the completed alignment cycle and remains amendable: later changes archive this confirmed page first and highlight what changed. confirmed means approved and current, not immutable.
docs/social-ledger-convention.md— new system-of-record convention (resolution, record schema, account scope, dedupe, gBrain link handling, public safety, X pattern, promo policy).docs/social-post-convention.md— added the ledger pointer and thepost_plus_repliescontext/skill-promo reply shape.docs/social/x-post-convention.md— added the main post + context reply + optional skill-promo reply pattern.docs/alignment-page-convention.md— BIP pages now ask for ledger storage scope, account identity, and public alignment URL status; 306ALIGNMENT-PAGE.mdbundles regenerated.scripts/skill-convention-registry.mjs,packages/skillpacks/scripts/build-package.mjs,packages/skillpacks/package.json— packagedassets/social-ledger-convention.md.tests/layer1/social-ledger-convention.test.tsandpackages/skillpacks/test/package-boundary.test.mjs— focused contract and packaging tests.
Approval source: compiled response YAML, response_status: complete, approval_status: ready-for-agent-review, all eight required gates answered, no unresolved negative or clarification feedback.
Table Of Contents
Context Captured
GeorgeQLe/me already has a Next route at /brain, public HTML copies under public/brain/<section>/, and sync scripts for alignment archives.
The agentic-skills alignment-archive sync moves source alignment HTML from this repo into gBrain.
A single account can post about multiple projects, so duplicate detection and promo cadence must be account-scoped, not only repo-scoped.
When a project has its own account, its ledger can remain local to that project with no central account ledger required.
Approved Model
The system of record resolves by posting identity first, then project. Shared personal or company accounts see prior posts across all projects, while project-owned accounts remain local. Implemented in docs/social-ledger-convention.md.
| Scope | Use When | Canonical Path | Agent Behavior |
|---|---|---|---|
| Project-local ledger | The project owns the posting account or posts do not need cross-project dedupe. | social/posts/*.yaml in the project repo. |
Read and write only local records for that project/account. |
| Central account ledger | One personal or brand account posts across many projects. | social-ledger/accounts/<account-id>/posts/*.yaml in a configured private central repo, defaulting to GeorgeQLe/me. |
Read account-wide history before drafting; write approved drafts and posted URLs to the central account ledger. |
| Both local and central | The project needs local provenance and the shared account needs account-wide dedupe. | Local mirror plus central canonical account record. | Prefer central for dedupe and status; keep local pointer or copy for project provenance. |
| Public gBrain projection | A public-safe alignment doc should provide context for a post. | https://6eorge.com/brain/<project-id>/<doc>.html. |
Link only approved public-safe docs; do not publish private ledger records by default. |
Ledger Record Shape
Each record is stable enough for later agents to answer what has already been drafted, approved, posted, linked, and promoted.
id: 2026-06-25-social-ledger-public-archive
account_id: george-x
project_id: agentic-skills
channel: x
topic: Social ledger and public archive
status: approved_draft
source_alignment_page: alignment/social-ledger-public-archive.html
public_alignment_url: https://6eorge.com/brain/agentic-skills/social-ledger-public-archive.html
drafting_mode: creator_inspired
post_mode: post_plus_replies
main_post: "..."
reply_chain:
- purpose: full_alignment_doc
text: "Full alignment doc for context: ..."
url: https://6eorge.com/brain/agentic-skills/social-ledger-public-archive.html
- purpose: skill_promo
text: "The workflow is powered by skillpacks: ..."
url: https://www.npmjs.com/package/skillpacks
published_urls: []
dedupe_fingerprint: "x:agentic-skills:social-ledger-public-archive"
risk_notes: []Records support draft, approved_draft, posted, skipped, needs_revision, and retired statuses. published_urls remains empty until a human posts manually.
X Posting Pattern
The approved X pattern is a main insight post, a first reply with the public alignment context link, and an optional second reply with a relevant skill/package link.
Must stand alone as the insight, lesson, result, or decision. It should not depend on the link to be useful.
Use a public gBrain URL when the alignment doc is approved for public context.
Use only when the post is actually about Agentic Skills, the workflow, or a reusable skill. Rotate wording to avoid repetitive promo.
Default to the npm package when install/use is the point; use GitHub when source, docs, or contribution context matters.
Public Safety Boundary
The canonical ledger stays private by default. The public surface is the sanitized alignment archive link and any post metadata the user explicitly approves — users approve what is put out publicly.
Before an agent proposes a public alignment URL, it verifies the source page is safe for public viewing and either already synced to gBrain or approved to sync.
Implementation Scope
The approved first build updated the Agentic Skills conventions so future BIP agents discover and use the ledger without re-asking from scratch every run. Automation scripts were deferred to a separate approval.
| Artifact | Purpose | Status |
|---|---|---|
docs/social-ledger-convention.md |
Define ledger resolution, record schema, account scope, duplicate checks, and public archive link handling. | Done |
docs/social-post-convention.md and docs/social/x-post-convention.md |
Add post-plus-replies output shape and the gBrain context reply / skill promo reply pattern. | Done |
docs/alignment-page-convention.md |
Teach BIP pages to ask for ledger storage, account scope, and public alignment URL status. | Done (306 bundles regenerated) |
| Package assets and tests | Publish the ledger convention in skillpacks and assert package visibility. | Done |
| Optional scripts | Validate ledger YAML, summarize recent account history, or sync central records. | Deferred (separate approval) |
Approval Record
Read-only record of the eight required gates and their answered decisions from the final compiled response YAML.
Gate 1: Public Archive Target
Use 6eorge.com/brain as the public archive target via GeorgeQLe/me /brain.
Gate 2: Ledger Storage Scope
Central account ledger for shared posting accounts; project-local ledgers only for project-owned accounts.
Gate 3: Account Resolution
Resolve mode, account_id, central_repo, central_path, and local_path from project config before drafting.
Gate 4: X Reply-Chain Pattern
Generate an X main post, a first reply with public alignment doc context, and an optional contextual skill-promo reply.
Gate 5: Skill Promo Policy
Contextual skill-promo replies with rotated wording; npm as the install target, GitHub as the source/docs target.
Gate 6: Public Safety Boundary
Keep canonical ledger records private; publish only public-safe alignment docs and approved post metadata.
Note: users approve what is put out publicly.
Gate 7: Implementation Scope
Build conventions, package assets, generated alignment guidance, and tests; defer automation scripts unless needed.
Gate 8: Artifact Paths
Use docs/social-ledger-convention.md, update the social and BIP conventions, package assets, and add focused tests.
target_path: docs/social-ledger-convention.md