- 技术分享Putting an agent inside a business system: five design principles from the engineering sideWiring agentic AI into an ERP is not about whether it can chat — it is about permissions, confirmations, audit and acceptance. Five engineering principles from real design reviews, plus an acceptance method that does not run on demo magic.
- 技术分享Account security in practice: trusted devices, token rotation and signing every session out on a password changeEverything after sign-in — remembering devices, issuing tokens, changing passwords — trades security against convenience. The rulebook for our own account system: four credential types, rotation with replay detection, and revocable-everything transparency.
- 技术分享"Connecting two independent account systems: one-time ticket SSO and three traps"Our parent-company site and product site keep separate account systems. No merged databases, no copied passwords — the connection happens at the session layer with a 120-second one-time ticket. The full design: claims, sequence, a security-properties table, and three traps cleared before launch.
- 技术分享'"Works locally, dies on deploy": a Docker environment-variable hijack postmortem'Same code, same commit — green locally, broken on deploy. The culprit turned out to be baked into the image. The full timeline, the probe commands, the before/after fix, and two guardrails kept.
- 技术分享"A small, complete endpoint: the design checklist behind delivering a contact form into CRM"The website's form endpoint does exactly one job — deliver enquiries into CRM reliably. Allow-lists, two-level rate limiting, idempotency semantics, decoupled notifications, privacy suppression: a step-by-step checklist where every line is a failure that will eventually happen in production.
- 技术分享Content architecture across two sites: why the docs live on the product site onlyThe parent site and the product site belong to the same company, but their content must stay in its place. Docs not forked, missing English honestly absent, every cross-link attributed, every legacy URL accounted for — the full trade-offs and checklists of a two-site content architecture.
