The contribution
Here / there · owns the photo
Reading the published contract…
- Contract
- —
- Revision
- —
- Visibility
- —
Reading the published contract…
Working exhibit · App Composer
Here / there collects photos. The owner approves them. Linkarooie features approved ones beside their own links. The second app does not own the photo, and it never keeps a copy.
Below is the published Here / there contract, read through this site. Both sides of it are on screen. Change the source and the composed card changes with it.
Here / there · owns the photo
Reading the published contract…
Reading the published contract…
Linkarooie · borrows the same photo
The card is not a copy of the photo. It is composed from the contribution, through the published contract.
Reading the published contract…
Reading the published contract… Read the story behind it
Second flow · App Composer
A visitor note, an approved public item and a featured card are three different states. This walkthrough follows one note through the published Here / there contract, then removes it at the source. It is a model of the contract, not a production control.
Reviewed against the maintained contract, Guestbook 019ce0d and Linkarooie 20ef9a5.
Owns the note, moderation and media.
Publishes the active invitation state, form path and limits.
Owns curation and the featured card.
Renders the send action and form link only for a validated open state.
Step 1 of 7
State: Open
The visitor meets the guestbook invitation
These controls move the explanation only. The source plate above is the working exhibit.
Linkarooie reads the exact Guestbook resource and shows the send action only when the invitation says open. Paused, closed, full or unavailable states keep the panel and explain the state.
Guestbook owns acceptance. Linkarooie owns the public invitation, and a malformed, redirected, foreign or partial answer becomes unavailable — never open.
SourceGuestbook manifest · Linkarooie invitation reader — Contract version 1, five states, exact resource and configuration.
The visitor's browser renders the postcard PNG; Guestbook validates and stores it as a pending private record, not a public item.
The visitor's words and media belong to Guestbook. Linkarooie never receives the guest code and never keeps a copy of the note.
SourceGuestbook resource contribution route — The resource route validates the postcard and starts it pending.
The pending item and its media are not public. A curator cannot turn a pending note into a card, because there is no public source item to reference.
Approval is an owner decision at the source. Featuring is a separate curation decision later; neither is a side effect of submission.
SourceGuestbook public resource — Public item and media follow the source's current visibility.
Guestbook makes the approved item public at its own address. The Linkarooie profile is still unchanged.
Guestbook owns moderation, publication, the item revision and the media. Approval is the source's publication decision; featuring remains a separate Linkarooie choice.
SourceGuestbook public resource — Approved public item; no automatic publication downstream.
Linkarooie collects the approved source into the profile. If the owner also pins it, the card appears in the Featured row. The card references the item; it does not copy the text or media.
Curation belongs to Linkarooie. The saved reference is the exact resource and configuration, so a later reviewable configuration advance does not silently point at another note. Collecting and pinning are separate owner choices.
SourceLinkarooie explicit collection — Collects a currently approved public item; never a pending one.
The item API and media return 404. The composed card disappears on the next public render, and no stale copy remains in Linkarooie.
Visibility is resolved at the source on every request. The card is a reference, so hiding or deleting at the source is enough; a downloaded copy cannot be recalled.
SourceGuestbook public visibility — Hidden items and media return 404; Linkarooie rechecks the source on render.
The panel explains the state and keeps a link to approved notes. No send action is rendered, and an already-public featured card is unaffected.
Acceptance and publication are different questions. Closing intake does not hide approved notes, and a full queue must not offer a form that would fail.
SourceMaintained contribution contract — Open, paused, closed and full; only open accepts a postcard.
Acceptance follows the source's current active configuration. A state is not a guess about what a form might do; it is what the contract returned.
Leave a note, using Guestbook's real form.
The guest code is shared by the owner separately; the note stays private until approval.
Postcards are paused; approved notes remain linked.
No send action is rendered while acceptance is paused.
Postcards are closed; approved notes remain linked.
Closing intake does not remove an already-approved public note.
The review queue is full; approved notes remain linked.
The limit covers 16 pending notes or 200 non-deleted items per linked resource.
The invitation could not be verified; no form or media link is shown.
A malformed, redirected, foreign or partial response never becomes open.
No contribution panel is shown.
Without an exact saved source and configuration there is nothing to ask.
A guestbook and a showcase could have been one app with two screens. They are not, and the difference is the whole point. They have separate repositories, separate deployments, separate storage and separate owners. The only thing that crosses between them is a versioned contract: a list of approved items, each with its own address, its own revision and its own visibility.
Because the showcase reads that contract rather than copying from it, one rule does the work. If the contribution is hidden or removed at the source, the feature disappears from the showcase on the next request. There is nothing to clean up in a second place, because there is no second copy.
If you are building a small system out of apps you already own:
The published Here / there contract, read through this site’s own read-only route. The photo is served by the guestbook; the card beside it is composed here, from the same record.
The visibility switch changes the demonstration only. Nothing is sent to the guestbook, no contribution is hidden, and nothing is deleted. The postcards are labelled fictional demo material by the source app itself.
Source plate 20 October 2026. Contribution flow 23 October 2026. Contract version 1, as published by the guestbook.