What must become possible?
Name the person, task, expected result, and observable evidence. Avoid beginning with a page count or preferred framework.
Route brief / no automated intake
Send coordinates a builder can actually navigate.
Write short answers. Unknown is an acceptable answer when it is labelled. Faith Forge Labs will use the brief for a fit check, not treat it as permission to begin.
What exists now?
List the software, data, vendors, ownership, access, workarounds, recent failures, and the parts that must stay available.
What changes for these users?
Note language variants, NOK or payment behavior, privacy choices, identity boundaries, formats, accessibility, and support expectations.
Who can decide?
Name the operator, technical contact, Norwegian content approver, vendor contact, specialist reviewer, budget owner, and release authority.
When must evidence be reviewed?
Provide decision dates, fixed external events, useful Norway-US overlap, and any time when an approver is unavailable.
What cannot be sacrificed?
Identify data, uptime, access, audit history, customer communication, backup, rollback, and support conditions required during change.
Direct base-camp contact
Email or call Faith Forge Labs.
Do not send passwords, private keys, personal datasets, or production secrets in the first message.