PTLam Architecturing

Answer one architecture question with a clear judgment: which option fits, why, what it gives up, what it assumes, and when to redesign. Size the answer for ten times today's numbers, not for infinity.

An architecture question decides structure that is expensive to reverse: how a system splits into components, runtimes, or data stores; a published surface such as an API, SDK, CLI, schema, file format, or plugin interface; where the true copy of state lives; or a commitment to a platform such as an OS, store, device, or offline use.

Not this skill: code layout one team changes in one release, business vocabulary, one failing run, or the written decision record on its own. This skill does not interview; send an open decision back to the caller. It writes a file only when the user names a destination.

Required skills