You open a questionnaire-driven matter, answer the formation questions at the terminal, and download the same artifact a
browser walk produces — the one you review before the staff-gated filing. matter open starts the onboarding__nest
matter and prints its notation id. intake answer then walks the formation questionnaire one question at a time — the
entity name, the registered agent, whether the company is member-managed or manager-managed, and the managing members
entered row by row (a blank name ends the list). Answer it interactively, or script it with repeated --answer and
--person flags. notation status reports the workflow state and whether the packet has already been rendered, then
notation approve renders and parks the filled packet for your review, and notation document writes the PDF to
--out. AIDA fills the state's official form from the answers — it never invents one — and the matter ends at the same
staff-gated filing__nv_sos step a browser walk reaches: you file with the Secretary of State; Navigator never files
for you.
This whole command-line round-trip is covered by an automated test that drives the real navigator binary and checks
the downloaded bytes are the official packet carrying the founder's answers. The pipeline behind the fill — vendoring
the canonical form, mapping answers to its fields, and the staff-gated filing that ends it — is laid out step by step in
Government forms: vendor, map, fill, file.