Decision: standalone entry target location #12

New issue

Closed

opened 2026-07-23 14:46:26 +02:00 by cloudbot · 2 comments

cloudbot commented

2026-07-23 14:46:26 +02:00

Collaborator

Decision — where do target_mode: standalone entries get created?

A template's App Config can route an entry one of two ways (§6):

append — adds a heading into an existing target doc (e.g. a member's canonical note). Location is fully specified by target_doc / position / heading_level. Settled.
standalone — creates a new document, title derived from the entry. The doc says it lands "at a configured parent (path/collection)" — but which parent is not decided. That's this issue.

Options for the standalone home

One dedicated collection (e.g. a "Logbook" / "Log Entries" collection) — every standalone entry lands there. Simplest; Stream reconstruction (§8) has one obvious place to search.
Per-template parent — each template's App Config names its own target_doc/collection, so e.g. appointment logs and shopping lists live in different places. Most flexible; more config per template and more collections for Stream to sweep.
Per-member parent — standalone entries nest under the member they're attributed to. Keeps a person's material together, but standalone entries aren't always member-scoped.

Whatever is chosen must be reachable by the Stream tab's documents.search / collections.list reconstruction (§8), and by collections.list for resolving the configured target.

What to decide

The default parent/collection for standalone entries (and whether templates may override it per-template).

Blocks: entry targeting for standalone templates, and the Stream tab's search scope.

Recommendation: a single dedicated collection as the default home, with an optional per-template override (target_doc/collection in App Config) for the cases that genuinely need it. This gives Stream one reliable place to look while leaving room for exceptions, without forcing per-template config on every template.

Source: Solution Design — Family App v1 §6, §8, §12 (doc vpBNbG4TsV).

**Decision — where do `target_mode: standalone` entries get created?** A template's `App Config` can route an entry one of two ways (§6): - **`append`** — adds a heading into an existing target doc (e.g. a member's canonical note). Location is fully specified by `target_doc` / `position` / `heading_level`. **Settled.** - **`standalone`** — creates a **new document**, title derived from the entry. The doc says it lands "at a configured parent (path/collection)" — but **which parent is not decided.** That's this issue. ### Options for the standalone home 1. **One dedicated collection** (e.g. a "Logbook" / "Log Entries" collection) — every standalone entry lands there. Simplest; Stream reconstruction (§8) has one obvious place to search. 2. **Per-template parent** — each template's `App Config` names its own `target_doc`/collection, so e.g. appointment logs and shopping lists live in different places. Most flexible; more config per template and more collections for Stream to sweep. 3. **Per-member parent** — standalone entries nest under the member they're attributed to. Keeps a person's material together, but standalone entries aren't always member-scoped. Whatever is chosen must be reachable by the Stream tab's `documents.search` / `collections.list` reconstruction (§8), and by `collections.list` for resolving the configured target. ### What to decide The default parent/collection for standalone entries (and whether templates may override it per-template). **Blocks:** entry targeting for standalone templates, and the Stream tab's search scope. **Recommendation:** a **single dedicated collection** as the default home, with an **optional per-template override** (`target_doc`/collection in App Config) for the cases that genuinely need it. This gives Stream one reliable place to look while leaving room for exceptions, without forcing per-template config on every template. **Source:** Solution Design — Family App v1 §6, §8, §12 ([doc vpBNbG4TsV](https://outline.marquezkeenan.family/doc/solution-design-family-app-v1-vpBNbG4TsV)).

cloudbot added this to the M0 · Open Questions & Decisions milestone

2026-07-23 14:46:26 +02:00

cloudbot added the

spike

label

2026-07-23 14:46:26 +02:00

cloudbot added a new dependency

2026-07-23 14:46:43 +02:00

#27 Entry targeting: standalone vs append