Shared reports

Reports that collect their own feedback.

Attach an HTML report to a task, organization, or project and share it by link. Readers pin comments, answer its question cards, and download a copy without a Kernel account, and you reply where they left them.

app.krnl.work/l/Hk2v…pQ/phase-2-findings.html

Northwind Robotics · Fulfillment APIPhase 2 discovery findingsPrepared for Dana Ito · October 6, 2026−62%Failed webhook deliveries180 msMedian event latency3Carriers left to migrateFindings1Webhook failures fell 62% once retries used exponential backoff. The remaining failures come from two carriers with expired signatures.2Event schema v2 removes three optional fields the warehouse team no longer reads.Q1Which rollout window works for your team?We can ship in the week of October 26 or the week of November 9.Answer this questionNext stepsMigrate the last three carriers to signed webhooks, then roll out schema v2 behind a flag for one warehouse before the rest.

Options

Feedback stays per link
Readers see only what was left through their own link, plus your replies. Separate recipients never see each other's comments or names.
Questions that get answered
Question cards in a report get an answer box. You can answer them too, from the page, when a decision report is addressed to you.
A copy for the reader
Readers download the version they're reading as a PDF printed on the server, or as the original HTML, or a ZIP when it has supporting files.

Reports, decks, atlases

Decks and story atlases take feedback too.

Kernel reads each HTML file's kind from its markup: a report, a deck, a user story atlas, or code. Choose the kind yourself for a hand-built file, and new links follow it.

On a deck, each comment belongs to its slide
On an atlas, comments and review notes follow their story page
Code is served exactly as stored, without Kernel's script

Northwind Robotics · Board reviewRisks before rolloutCarrier sandbox access is still pending1Two carriers still sign webhooks with expired keysThe EU warehouse freezes changes from Nov 13 / 8Comments×1On: “Carrier sandbox access is still pending”Slide 3Dana Ito 2 minutes agoCan we unblock this before the 26th?Options1

Author mode

Open your own report and answer in place.

Opened from Kernel, a report carries private feedback that only you see. On one of your links you are its author, and reply, resolve, and answer question cards under your own name.

Private feedback needs no link and never appears on one
View as reader shows the page as that link's readers see it
Readers edit or delete only what they posted from their browser

Northwind Robotics · Fulfillment APIPhase 2 discovery findingsWebhook failures fell 62% once retries used exponential backoff.1Q1 Which rollout window works for your team?Comments×OpenResolvedAll1On: “Webhook failures fell 62% once retries used…”Resolved by Sam CarterDana Ito 6 minutes agoCan we see the same numbers for the EU carriers?Sam Carter Author just nowYes. They’ll be in version 3 this week.ReplyReopen

Good to know

A file can have up to 20 links, each with its own label and its own Disable switch.
A link shows the latest version or stays on one, and its address never changes.
Views skip your own opens, chat previews, and crawlers, and store no IP address.
Each version's PDF is printed once on the server and shared by every link to it.
Kernel doesn't send links or notify you of feedback, and never writes it into the file.
Comments follow their element into later versions, or are listed as Detached.

Highlights

Feedback stays per link

Questions that get answered

A copy for the reader

Decks and story atlases take feedback too.

Open your own report and answer in place.

Good to know

Works well with