We built four layers. Then a link walked through the wall.
On 2026-07-24 we wrote down the whole stack on a single page. Four layers. One rule that mattered more than any policy memo: decide the layers once and encode the divider into the production line.
Open layer: findings and proof, free to cite. Member layer: everything runnable. Boxed delivery: finished systems we ship into a customer’s data at a fixed price. Internal layer: the machinery that never appears anywhere.
We thought the wall between open and member was simple. We had a password page. We had a members’ library. We had a guiding sentence in every public flagship that pointed readers toward the member materials.
The audit that changed the day
Same day, we ran an audit. Quick test. Someone grabbed a direct file link from the library and pasted it into a private browser. The file opened without a password.
Not blurry suspicion. Repeatable. We tried again from another account. Same result. A link bypassed the gateway every time.
We then removed access and tried again. The link failed. We flipped the sharing flag back on. The file opened. That flip was the moment it clicked.
The file system’s sharing settings, not the password page, controlled real access. The wall had a leak: links behind the wall had their own access rules.
What this taught us
Finding one: the dividing rule belongs in code. We made the production line enforce the split so an open article never contains the runnable checklist; instead one line points to the members’ library. That sentence stays. The runnable thing lives behind the membership gate. The code refuses to render the runnable artifact into the open page.
Finding two: proof stays open on purpose. We kept evidence blocks visible because proof is what gets cited by others and by machines that crawl and verify claims. We tested locking a proof block and saw immediate drop-offs in citation and reuse during our short crawl window; making the same proof open again restored those signals.
Finding three: one generous flagship guide per topic anchors authority. We produced a public flagship that gives away a lot to demonstrate competence. Its executable companion—the checklists and templates that would let someone run the system—lives inside membership. Our traffic and conversion behavior showed the flagship increased trust; members accessed the companion materials next.
Counter-example: we once considered locking proof to drive members. It failed. Evidence behind a gate reduced third-party references and made the flagship seem hollow. The experiment made the choice clear—the open evidence is the trust engine.
The rule that fell out
Decide the layers once. Encode that decision into the production line. Make open pages contain findings and proof only; include exactly one sentence that points to the members’ library for anything runnable. Then audit every shared link before you promote the library.
One concrete detail we left in the open: each flagship article contains a single sentence that reads like an invitation and points readers to the members’ library. That sentence is intentionally minimal; it does not include runnable materials.
What we did next felt surgical. We swept the library for permissive shared links, tightened file sharing so links required login, and added a pre-publish check that refuses to publish a flagship if any file behind it has a public link. The runnable, tested version of this enforcement lives in the members’ library.
How we know
The audit produced reproducible failures and fixes. A direct link opened files without authentication. Removing the link closed access. Restoring the link reopened access. We logged the events. We measured citation behavior when proof blocks were locked and unlocked. We measured membership pull from flagships. The patterns repeated across topics.
Questions we got
Why keep proof open if members pay for depth?
Proof is the trust layer. Open evidence gets cited and builds authority for the whole site. Locking it hurts discoverability and external verification, which reduces long-term value for members too.
Won’t telling people where the runnable stuff is invite scraping?
It will draw attention. That’s the point. But attention is controlled: the public pointer is just a sentence. The executable assets stay behind login and tightened sharing. Make the pointer visible; make the assets harder to access.
How often should we audit sharing settings?
Often enough to catch changes before promotion. We run a targeted audit whenever we plan to promote a flagship. We also added automated checks in the production line so the system refuses to publish if any linked file is public.
Decide the layers. Code the rule into the machine. Remember: a wall is only as tight as every link behind it.
Sources: internal production notes and the same-day audit of our content and sharing settings (2026-07-24).
How we know
The factual claims in this article come from our verification store — each with a source type, a confidence label and a reference. The method is documented on How we know.
– Proof blocks stay in the open layer on purpose: evidence is what gets cited and what builds trust with both readers and machines, so putting it behind a wall would defeat the reason it exists. | source: first-hand experience | conf: observed | ref: Fordelingsnøkkel v1 (2026-07-24) — bevisblokk åpen med vilje
– On 2026-07-24 we sorted everything we know into four layers with one page as the ruling: open findings and proof anyone can cite, runnable material for members only, finished systems delivered on a customer’s own data at a fixed price, and the internal machinery that is never published at all. | source: first-hand experience | conf: observed | ref: Fordelingsnøkkel v1 (2026-07-24) — Prinsippet (4 lag)
– Each topic gets exactly one deliberately generous flagship guide that gives away a lot on purpose to anchor authority, while its runnable companion — the checklists and templates that make it executable — lives behind the member wall. | source: first-hand experience | conf: observed | ref: Fordelingsnøkkel v1 (2026-07-24) — flaggskip-unntaket
– It is assumed a password page protects gated content — the same-day audit of our own setup found that direct file links bypassed the member password entirely, so anyone with a shared link walked straight past the wall. The rule: a paywall is only as tight as every link behind it, and sharing settings must be audited before the library is promoted. | source: documented source | conf: mythbuster | ref: Fordelingsnøkkel v1 (2026-07-24) — ‘⚠️ Gap: Drive-deling på skill-filene må strammes (lenke-tilgang omgår passordet)’
Leave a Reply