Episode 4 - Review, publish, and preview
This episode ends the core path by reviewing the article and marking its source public. If Docker is available, you will also render a local preview; a production URL remains a separate deployment setup.
1. Review the public claim
Read the article as someone who does not know the project:
- Do the first two sentences state what changed and why it matters?
- Can the reader find the evidence?
- Is the uncertainty visible?
- Does the title use terms another researcher would search for?
- Is every remaining sentence safe to make public?
If an Agent prepared the change, inspect the proposal first:
silan proposal list
silan proposal show <id>Accepting a proposal changes source files. It still does not publish or deploy the item.
2. Publish the reviewed source
silan blog publish new-research-result
silan content lint
silan index sync
silan blog show new-research-resultConfirm that the article is published and public. This is the end of the CLI-only success path: the authored source now records your deliberate decision to publish.
3. Render a local preview
Preview needs a running Docker daemon:
docker --version
docker compose version
docker info >/dev/nullFirst inspect the planned operations:
silan site previewThen run them:
silan site preview --confirmOpen http://localhost:8080 and check:
- title, opening, and evidence links;
- images and language switch;
- related project or
updatelinks; - mobile and desktop reading;
- absence of private notes.
The full Docker and desktop verification record, including environment issues and recovery steps, lives in the E2E report. It is reference material, not required reading for the first update.
4. Understand the production boundary
Silan Viking does not choose a hosting setup for you. A production deployment needs:
- a reviewed
[deploy]section insilan-viking.toml; - SSH credentials and a reachable target;
- Docker on that target;
- a dry run that names the intended host and operations.
silan site deploy --dry-run
silan site deploy --confirmDo not run the confirmed command until the dry run matches the target you intend to update.
5. Ask an Agent to prepare the next maintenance pass
After the first article exists, a bounded Agent request becomes useful:
Find the project and résumé records related to this article. Prepare a
proposal for any stale description, preserve the uncertainty, and report
which public surfaces still need my decision.
For an MCP-compatible client:
silan skill emit
silan mcp serve --stdioReview resulting changes with:
silan proposal list
silan proposal show <id>The Agent can retrieve context and prepare maintenance. The owner keeps acceptance, publication, and production deployment.
6. Interpret feedback narrowly
After a real deployment, inspect delivery before attention:
- Does the deployed content version match the reviewed source?
- Did humans open the article or only the index?
- Did a request classified as a search-engine or AI crawler reach the page?
- Does a comment expose a missing explanation?
A visit is not a full reading, and a crawler request does not imply indexing, understanding, ranking, or citation. The next useful action may be a clearer opening, one evidence link, another language, a delivery fix, or no change.
You have finished the series when one real update exists as reviewed public source and you understand exactly what additional setup is required to make it a live site.
No comments yet