alignment_status: review
Social Ledger and Public Archive Decisions
This page records the proposed decisions for building a cross-project social post system of record, public-safe gBrain alignment links, and channel-specific reply-chain patterns for build-in-public posts.
GeorgeQLe/me repo, or change social conventions. Implementation starts only after compiled response YAML has approval_status: ready-for-agent-review.
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 section in scripts/alignment-archive.config.mjs syncs 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.
Proposed Model
The system of record should resolve by posting identity first, then project. That lets shared personal or company accounts see prior posts across all projects while project-owned accounts remain local.
| 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 should be 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 should support draft, approved draft, posted, skipped, needs revision, and retired statuses. Published URLs can remain empty until a human posts manually.
X Posting Pattern
The preferred 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 should remain private by default. The public surface is the sanitized alignment archive link and any post metadata the user explicitly approves.
Before an agent proposes a public alignment URL, it should verify the source page is safe for public viewing and either already synced to gBrain or approved to sync.
Implementation Scope
If approved, the build should update the Agentic Skills conventions so future BIP agents can discover and use the ledger without re-asking from scratch every run.
| Artifact | Purpose | Approval Needed |
|---|---|---|
docs/social-ledger-convention.md |
Define ledger resolution, record schema, account scope, duplicate checks, and public archive link handling. | Yes |
docs/social-post-convention.md and X child convention |
Add post plus replies output shape and the gBrain context reply / skill promo reply pattern. | Yes |
docs/alignment-page-convention.md |
Teach BIP pages to ask for ledger storage, account scope, and public alignment URL status. | Yes |
| Package assets and tests | Publish the ledger convention in skillpacks and assert package visibility. | Yes |
| Optional scripts | Validate ledger YAML, summarize recent account history, or sync central records. | Separate approval unless selected below |
Approval Gates
Gate 1: Public Archive Target
Where should public-safe alignment context links resolve?
Gate 2: Ledger Storage Scope
How should social post records be stored?
Gate 3: Account Resolution
How should agents decide whether to read a local or cross-project ledger?
Gate 4: X Reply-Chain Pattern
Should BIP output support the main post plus replies pattern?
Gate 5: Skill Promo Policy
How should recurring skill promotion links work?
Gate 6: Public Safety Boundary
What public/private split should agents enforce?
Gate 7: Implementation Scope
What should the first build include?
Gate 8: Artifact Paths
Which canonical artifact paths should the build target?
Compile Responses
Use this section to compile gate answers and selected section feedback into YAML. Complete approval requires all eight required gates answered and no unresolved negative or clarification feedback.