Real, currently-unresolved ambiguities worth knowing about before you assume something — not a decision log. This page defers to each agent's own STATE.md and this repo's README.md for anything about who decided what and when — those stay canonical; this page is just a navigational index of what's still open, so it doesn't become a second, drifting record of decisions.
flme.ai (see hearth/STATE.md). (2) A separate folder, ReqDoc/Requirements/Specstrum/, holding its own parallel Core/Functions/Process requirements content. Whether these two are related (e.g. #2 is the spec framework for product #1) hasn't been confirmed — treat them as two facts sharing one name until someone checks.marlowe/research/naming-brainstorm-2026-08-31.md) with a leading unverified candidate, deliberately not repeated here since it isn't decided.backend vs. backend-template naming is easy to get backwards. backend is the reference/template copy; backend-template is also the reference/template repo. Neither is a client. Real clients are browser and (superseded) petstore. See the Repo Atlas.Requirements/Specstrum/ and Requirements/Core/ is unconfirmed. The Specstrum folder mirrors Core's own structure (its own Standards, Skills, Reviews, Tools) — mirror, fork, or successor is not established. Don't assume either without checking with whoever's been working in ReqDoc directly.ux-tools out of ux-template — some of it may still only exist in ux-template/docs/, some in ux-tools's own files. Check both before assuming one is current.