kotona.app

Log

Publication and project log

Published notes and verified project states are generated from content metadata. Site-level changes remain a small manual record.

  1. Published note: The cluster did not need another lock.
  2. Machine-surface repairs: the Agent Skills index digest is now generated from the artifact and drift-checked in CI, a superseded note carries its declared successor into Explore results, and the browser suite became a CI gate. Term tooltips no longer clip outside the viewport, acronyms render with their real casing, and note metadata distinguishes a note's role from its claim posture.
  3. Verified project state: vuoro.
  4. Published note: The workshop disappeared. The hotspots survived..
  5. Published note: Governance for a team of one.
  6. Published note: The human is in the slow loop.
  7. Published note: The next prompt was only the visible error.
  8. Published note: The platform can retrieve; the application still has to decide.
  9. Published note: The queue was never the hard part.
  10. Verified project state: acceptance-lab.
  11. Published note: A platform capability does not exist all at once.
  12. Published note: Why production access changes the shape of agent tooling.
  13. Published note: A merged PR is not an architectural decision.
  14. Published note: Measure the diagnosis, not only the transcript.
  15. Added the Explore knowledge atlas and public graph endpoint; revised the editorial guide and core notes toward operationally grounded prose.
  16. Published note: A reference architecture is a hypothesis library.
  17. Published note: Plan migrations through verified intermediate states.
  18. Published note: The recommendation does not need authority.
  19. Published note: Account for node-local state in GitOps recovery.
  20. Published note: Treat project folders as views over authoritative state.
  21. Published note: The candidate passed. The upgrade did not..
  22. Published note: The wallpaper is a build artifact.
  23. Published note: What 107 isolated completions did not show.
  24. Published note: Authority must travel with the action.
  25. Site refactored around explicit note roles, lifecycle succession, and clearer discovery surfaces.
  26. About page rewritten to reflect the site's expanded scope, content lifecycles, and agent-assisted authorship.
  27. Published note: A field guide to assurance-managed AI development.
  28. Published note: A personal knowledge system that happens to render as a website.
  29. Published note: The candidate produced somewhere else.
  30. Published note: Where the assurance questions are already answered.
  31. Published note: Where the cohort comes from.
  32. Published note: Why I publish explore prompts.
  33. Explicit note lifecycles, retrieval evaluation, an editorial-model link, and deployed revision metadata added.
  34. Navigable tag pages, generated per-content social cards, and accessible project terminology notes added.
  35. Project evidence blocks, optional metadata titles, structured data, a privacy disclosure, and code-owned security headers shipped.
  36. Published note: Derive status only from reproducible evidence.
  37. Published note: Design internal pipelines for succession, not just operation.
  38. Published note: Legibility is an operating property.
  39. Published note: Size the spa to the river.
  40. Published note: The agent is not the application.
  41. Published note: The deployment boundary was only a place.
  42. Published note: The devbox is an access cell.
  43. Published note: The junior ladder was a joint product.
  44. Published note: The paragraphs are cheap. The embarrassment is mine..
  45. Published note: The patch was open source's proof of work.
  46. Published note: The person of record.
  47. Published note: The second operator is the test.
  48. Published note: The work between the ticket and the agent.
  49. Published note: The workshop is learning my accent.
  50. Verified project state: homelab-analytics.
  51. Published note: Judge agents by the next prompt.
  52. Published note: The ref nobody adds.
  53. Verified project state: appservice.
  54. Verified project state: box.
  55. Published note: Delivered energy.
  56. Published note: Layering you can't violate by accident.
  57. Published note: Moving a live cluster to a new subnet.
  58. Published note: NFC tokens pointing at a manifest.
  59. Published note: Subprocess, not service.
  60. Published note: The aftertaste of resolution.
  61. Published note: The coordinator never touches the repo.
  62. Published note: Log as system.
  63. Published note: Schema on split.
  64. Published note: The missing layer is binding, not intelligence.
  65. About page updated: name, Helsinki, professional context now lead.
  66. Household operating platform project page rewritten with motivation section.
  67. Project schema extended with kind field; projects index now groups by Repositories and Worlds.
  68. Site changelog added at /log/.
  69. sprintctl and kctl project page published.
  70. Eight writing posts published as launch batch.
  71. Household operating platform project page published.
  72. Published note: A GitOps rollback needs time to reach Git.
  73. Published note: Compatibility reports should be a little rude.
  74. Published note: The boring auth boundary was right.
  75. GitOps cluster project page published.
  76. Contract-first box project page published.
  77. Site launched on Cloudflare Pages.