# Daily book extraction — web-published Markdown mirror

Use this pattern when a recurring book digest accumulates tools/questions/insights in Markdown and the user also wants a phone-accessible browser page that shows the growing base.

## Pattern

1. Keep one canonical Markdown source.
   - If a public Markdown/wiki site already exists, create a new article/page there.
   - Symlink the book pipeline’s accumulating file to that website article instead of maintaining two separate files.

2. Preserve website metadata.
   - Add YAML frontmatter required by the site, e.g. `title`, `slug`, `category`, `summary`, `links`.
   - Update the cron prompt so future runs append below the frontmatter and never overwrite it.

3. Connect the page into navigation.
   - Add a wiki link from the site index or portal page if the site’s UI discovers pages from Markdown files.

4. Update the cron prompt.
   - Mention the public URL.
   - Tell the future agent that `accumulating_file` may be a symlink to a website article.
   - Tell it to add a new day section rather than rewriting the whole base.

5. Verify before reporting.
   - Check the symlink or canonical file path.
   - Confirm the site process or static host reads that directory.
   - Fetch the public URL/API if available.

## Example layout

```text
/book_project/TOOLS_QUESTIONS_INSIGHTS.md -> /wiki/content/cosmic-trigger.md
/wiki/content/cosmic-trigger.md
/wiki/content/index.md  # contains [[cosmic-trigger|...]]
```

## Prompt line to include

```text
Important: accumulating_file points to a Markdown article used by the public website. Preserve YAML frontmatter at the top of the file and append the new day’s section below current content. Public page: <URL>.
```