BIP Drafting — Positioning Synthesis

Build-In-Public selected-channel drafting review for /positioning --synthesize research/afps-tracker. The target-channel selection gate was approved and consumed (LinkedIn + X). This page now presents the drafting-stage gates: drafting mode, content angles, channel-specific sample posts, tone, claim safety, and publish readiness. Approving everything compiles final BIP YAML (bip_approval_status: ready-for-agent-review) so the agent can record the BIP decisions and return to the normal synthesis page's final artifact approval. This page does not publish anything and does not write canonical artifacts.

Alignment statusreview
Page kindbip drafting
Gates the pagepositioning-synthesis-afps-tracker.html
Alignment date2026-06-29

Channel Selection — Approved & Consumed

The target-channel gate compiled bip_channel_selection_status: ready-for-agent-review approving the pre-selected recommended set. Drafting below proceeds only for these channels:

LinkedIn selected platform_aligned

Loaded convention
docs/social/linkedin-post-convention.md (via router docs/social-post-convention.md)
Why this channel
Professional, work-contextual audience; strong fit for founder method/lesson posts. Build-in-public process narrative is source-safe at the pre-product stage.

X (Twitter) selected creator_inspired

Loaded convention
docs/social/x-post-convention.md (via router docs/social-post-convention.md)
Why this channel
Fast public conversation among indie/AI-dev builders; short hooks and threads on positioning method fit the audience.

Source-Safety Posture — Pre-Product Hypothesis (carried forward)

The positioning is an explicit pre-product, hypothesized position: no shipped product, no live users, no validated metrics, no proven WTP. Every draft below is framed as method / process storytelling or a clearly-labeled hypothesis. None claims a shipped capability, launch, availability, metric, customer, or competitor name. Phrases like “a tool I’m designing,” “a hypothesis I’m testing,” and “still to validate” are load-bearing — do not strip them when editing.

1. Drafting Mode

Each selected channel uses one drafting mode. The agent-recommended mode is pre-selected; switch either if you prefer. platform_aligned stays conservative and close to platform rules; creator_inspired uses stronger hooks and narrative framing labeled as practitioner norm (never overriding source safety).

LinkedIn drafting mode

X drafting mode

2. Content Angles

Each angle is drawn directly from the completed Stage 2 synthesis and is source-safe. Angles A–C are pre-selected; D is optional (thinner milestone post). Uncheck any you don’t want drafted; the sample posts in section 3 are grouped by angle.

recommended

Type
Method / process storytelling
Source basis
The positioning run itself: jtbd-positioning → strategic-canvas → moore-positioning, and the synthesis’s evidence-vs-assumption mapping.
Audience
Founders, PMs, indie builders doing early positioning.
Why publish
Teaches a repeatable method; zero product claims; the “triangulate across frameworks” takeaway is genuinely useful.
Risk / claim risk
Low / low.

recommended

Type
Hypothesis-framed thought piece
Source basis
Strategic-canvas blue-ocean gap + Moore compressed claim: “navigable like a board, faithful like the files.”
Audience
AI-workflow operators, dev-tool builders.
Why publish
The core differentiating insight; opinionated but honest as an open hypothesis.
Risk / claim risk
Low–medium / low–medium — must keep explicit hypothesis framing; no “we built it” implication.

recommended

Type
Lesson learned
Source basis
Strategic-canvas Eliminate (collaboration at v1) + Reduce (write-back → read-first; feature breadth); positioning lesson “broadening weakens the wedge.”
Audience
Founders / product people.
Why publish
Counterintuitive, concrete lesson (cutting features competitors add is the position); strong narrative.
Risk / claim risk
Low / low — framed as v1 hypotheses, not shipped scope.

optional

Type
Build-in-public milestone
Source basis
Completion of the positioning stage in the AFPS research chain.
Audience
Followers of the build-in-public journey.
Why optional
Thinner value than A–C; a simple checkpoint. Include only if you’re posting a regular BIP cadence.
Risk / claim risk
Low / low.

3. Sample Posts

One channel-specific draft per selected angle × channel. Mark each approve, revise (note the change), or reject. Drafts default to approve. Character counts are advisory; X targets ≤280 per post, LinkedIn keeps the point in the first 2–3 lines.

Angle A — Method (3 frameworks)

LinkedIn · platform_aligned single_post

Before writing a line of product code, I ran a positioning pass on a tool I'm designing — and deliberately forced it through three frameworks instead of one. Jobs-to-be-Done to name the actual job. Blue Ocean's value curve to decide what to cut, not just what to add. Geoffrey Moore's template to compress it into a single testable sentence — explicitly a hypothesis, not a claim. The most useful output wasn't the tagline. It was a map of which parts of the position are evidenced versus still assumed — so I know exactly what to validate before building anything. If you're positioning something pre-product, triangulating across a few frameworks surfaces the gaps that any single framework quietly hides. #positioning #productstrategy
Source basis
Positioning run manifest + synthesis evidence/assumption register.
Claim-safety notes
“a tool I'm designing” + “hypothesis, not a claim” keep it pre-product. No metrics, no product name.
Publish precheck
Keep hashtags sparse; no link needed.

X · creator_inspired thread

Positioned a pre-product tool today without writing any product code. The trick: don't trust one framework. I ran JTBD → Blue Ocean → Moore and let them argue with each other. The gold wasn't the tagline. It was the map of what's evidenced vs. what's still a guess. 🧵
↳ JTBD named the real job: not "a dashboard," but "rebuild trust in my project's state after a restart or handoff." Different job → different product.
↳ Blue Ocean's value curve was the forcing function. It made me decide what to *eliminate*, not just what to add. Subtraction turned out to be the position.
↳ Moore compressed it to one sentence — framed as a hypothesis. Now I have an explicit list of what to validate before I build. That list is the actual deliverable.
Source basis
Same as LinkedIn A; thread beats map to JTBD / Canvas / Moore steps.
Claim-safety notes
“pre-product” stated in post 1; each reply is method, not capability. No metrics.
Post mode
post_plus_replies as a content thread (no external/context link). Each reply purpose: thread_continuation.
Publish precheck
Each post ≤280; no screenshots.

Angle B — Thought piece (navigability vs. fidelity)

LinkedIn · platform_aligned single_post

A hypothesis I'm testing while positioning a research-workflow tool: Most tools make you choose between navigability (a clean board or dashboard view) and source fidelity (your real files staying the source of truth). Dashboards duplicate state; files stay trustworthy but get hard to navigate. The interesting gap is the combination neither side offers: navigable AND faithful — a read-first view over the canonical files, where every claim links back to its source and nothing is duplicated or mutated. I don't have proof yet — it's a positioning hypothesis, not a shipped feature. But the gap itself looks real. When have you been forced to choose between a tool that duplicates your state and one that just reads from the source?
Source basis
Strategic-canvas blue-ocean gap; Moore compressed claim.
Claim-safety notes
Explicit “hypothesis, not a shipped feature”; ends with a genuine question, not a CTA.
Publish precheck
No hashtags needed; no link.

X · creator_inspired single_post

Positioning hypothesis I keep circling back to: PM tools make you pick — navigable OR faithful to your real files. Boards duplicate your state; files stay true but get unnavigable. The open lane: navigable AND faithful. Read-first over the source, every claim linked back, nothing duplicated. (Hypothesis, not a shipped thing — yet.)
Source basis
Same as LinkedIn B.
Claim-safety notes
Parenthetical hypothesis disclaimer required; compression risk — do not drop it.
Post mode
single_post (no context link).
Publish precheck
≤280; no hashtags required.

Angle C — Lesson (discipline of subtraction)

LinkedIn · platform_aligned single_post

The hardest part of positioning wasn't deciding what to build — it was deciding what to leave out. While positioning a pre-product tool, the value-curve exercise pushed three deliberate subtractions for a first version: • No multi-user collaboration surface — the wedge is the individual operator. • No write-back into the canonical files — read-first, because the biggest adoption fear is a tool corrupting your source of truth. • No broad workspace features — staying thin protects the trust story. Every one of those is something competing tools add. Choosing to cut them is the position. Subtraction is a strategy, not a gap. (All still hypotheses to validate — but the discipline is the point.)
Source basis
Canvas Eliminate/Reduce moves; positioning “broadening weakens the wedge” lesson.
Claim-safety notes
“pre-product” + “hypotheses to validate”; no competitor named; “competing tools” is generic.
Publish precheck
Bullets render on LinkedIn; no link.

X · creator_inspired thread

Positioning lesson today: what you *cut* is the position. For a tool I'm designing, the value-curve work pushed 3 deliberate v1 subtractions: - no collaboration surface - no write-back to your source files (read-first) - no broad workspace features Competitors add all three. Cutting them is the wedge.
↳ The write-back cut is the sharpest. The #1 adoption fear for this kind of tool is it quietly corrupting your canonical files. Read-first neutralizes that — you trade "powerful" for "trusted." (Hypothesis, not proof yet.)
Source basis
Same as LinkedIn C; Reduce(write-back) = Anxiety force.
Claim-safety notes
“v1” + “hypothesis, not proof yet”; generic “competitors.”
Post mode
post_plus_replies content thread; reply purpose: thread_continuation.
Publish precheck
Each post ≤280.

Angle D — Milestone optional — only drafts if angle D is checked

LinkedIn · platform_aligned single_post

Build-in-public checkpoint: just finished the positioning synthesis stage for a research-workflow tool I'm working on. Three frameworks (Jobs-to-be-Done, Blue Ocean, Geoffrey Moore) compiled into one testable position — plus an explicit map of what's evidenced versus what's still an assumption. Next: pressure-testing the assumptions before any build. Onward.
Source basis
Positioning stage completion in the research chain.
Claim-safety notes
“a tool I'm working on”; no product name, no metrics.
Publish precheck
Only post if angle D is selected.

X · creator_inspired single_post

BIP checkpoint ✅ positioning synthesis done. 3 frameworks → 1 testable position + a map of what still needs validating. Next stop: pressure-test the assumptions before building anything.
Source basis
Same as LinkedIn D.
Claim-safety notes
No metrics; “before building anything” keeps it pre-product.
Publish precheck
≤280; only post if angle D is selected.

4. Post Mode & Context Link

The X threads above are content-only (post_plus_replies with each reply a thread_continuation) — no external link. A public alignment context link (gBrain projection) would require an approved, public-safe doc and the social-ledger contract. Neither is set up: .agents/project.json social_ledger is unset and no public gBrain doc exists for this project yet.

Public alignment context link & ledger

Optional skill-promo reply on the method posts?

Angle A & the milestone are genuinely about the Agentic Skills positioning workflow, so a single rotated promo reply (npm / GitHub) would be on-topic. Default is to skip it to stay non-promotional at the pre-product stage.

5. Tone

Target tone: specific, generous, and concrete; honest about the pre-product/hypothesis status; no triumphalism, hustle language, or virality bait. LinkedIn leans professional; X leans conversational but still sourced.

Approve the tone across the drafts?

6. Claim Safety

Every draft is checked against the source-safety rules: no unsupported performance/adoption/revenue/benchmark claims, no private repo/customer context, no secrets, no customer/competitor names, no unverifiable “first/best/only,” no premature roadmap/pricing/availability commitments. The pre-product status is stated or implied in each draft. Competitors are referenced only generically.

Approve claim safety?

7. Publish Readiness

Publish readiness confirms the approved drafts are ready for you to post manually. This page never publishes. Prechecks: hashtags sparse and relevant; X posts under 280; no screenshots; no link requiring an unapproved public doc.

Approve publish readiness for the selected/approved drafts?

Compile Final BIP YAML

When the gates above are answered with no revision/hold flags, this compiles final BIP YAML (bip_approval_status: ready-for-agent-review). Paste it into a session running /positioning --synthesize research/afps-tracker. The agent records the approved BIP decisions in the Stage 2 review record and returns to the synthesis page’s final artifact approval flow. Any revise, hold, reject-all, or clarification keeps the page in review and routes back instead of granting final BIP approval.