Skip to content
Intentset

Lantern, a worked example · Review page

Publication readiness

An invented example

This Atlas is drawn from the records of an invented product, so it can be published to show what the Atlas shows. A team's own Atlas may contain internal and restricted records and stays inside the organization. The files are authoritative; these pages are a derived view of them.

Snapshot: commit unknown · graph hash 6914e830beab · level L1 · scope examples/scheduling/**

Which projection would publish each knowledge artifact, checked by the publisher's own projection: deny by default, every availability dimension intersected, drafts and retired records excluded, and review current against the sources it explains. Each projection is checked with one request built from the knowledge's own audiences and availability, taking the first value of each list in code-unit order. References and titles are checked only when documents are generated, so a projection that admits a record here can still refuse its document.

Knowledge artifacts: 1. Review current: 1 of 1 knowledge artifact. Admitted by at least one projection: 1 of 1 knowledge artifact.

Projection Admits visibility Authorization the request carries
public public none needed
customer public, customer none needed
internal public, customer, internal internal
restricted public, customer, internal, restricted internal and restricted

KB-ASMT-SCHEDULE: Prepare a scheduled student assessment

knowledge · status approved · owner team-assessment · examples/scheduling/KB-ASMT-SCHEDULE.md · its page

Projection Admits Result
public public excluded visibility
customer public, customer would publish
internal public, customer, internal would publish
restricted public, customer, internal, restricted would publish

Checked as audience teacher, product PRD-LANTERN, release pilot-1, role teacher, edition standard, flags none.