pre-submitlisted

# pre-submit **Run this with the form open and everything filled in, before the button.** Everything here is unfixable afterwards. An application is the one artefact in this system with no undo: the recruiter's first read is the only first read there is, and nobody writes back to say which line lost it. **Work through it in order. Report what passes as well as what fails** — a check that only ever produces problems stops being run. --- ## 1. Is it still the right decision? **Ask once, plainly, and accept the answer.** - **Does it still clear the threshold?** If the score moved since the pack was built — a work pattern confirmed, a salary discovered — say so now. **A role that dropped below the bar is worth ten minutes of awkwardness, not three weeks of process.** - **Is anything still unknown that would decide it?** If the deciding fact is unresolved, applying is usually still right, but they should know they are applying to find it out. - 🔴 **Is the posting still open?** Check again if the pack was built more than a few days ago. ## 1.5 🔴 is there a market standard to build against? **Check `vault/wiki/` for all four market-standards pages, and check their `stale_after` has not passed.** **If missing or stale, say so plainly — name the page and why it matters for the artefacts about to be submitted** (*"nothing here knows whether a two-page CV is the norm in your market, or whether a cover letter is expected at all"*). **Then offer `/market-standards`**, an