Formation Evidence

§11.3 describes the genesis process a Humanized Autonomous Organization (HAO) — the network’s coordinating framework — expects its first United Micro Enterprises (UMEs) — small, self-managing venture teams of up to ~15 people — to follow: a Letter of Intent with no stated duration, then a Provisional Operations stage with an explicit three-to-six-week target window. Nothing in the deployment chapter states how long entity formation itself — the legal and financial mechanics underneath that first step — actually takes in practice. This section supplies the corpus’s only real-world timing data on that question, drawn from two source documents: a timestamped log of a single entity-formation process, and a document describing the model as it was presented to an outside pitch audience. Both describe a single instance and are presented as such, not as a general rule.

11.7.1 A Measured Formation Timeline

The corpus’s only measured entity-formation datapoint comes from a same-day log of forming provide.io as an Oregon limited liability company (LLC). The log’s stated purpose was to measure how long forming an entity could take, from no entity in existence to an account ready to receive funds. Over the course of one calendar day, the following was completed: the LLC filed with the Oregon Secretary of State, a domain registered, an Employer Identification Number (EIN) obtained from the US Internal Revenue Service (IRS), a Google Workspace account provisioned, and a business bank account opened with Mercury and approved.

Timestamped sequence, preserved as recorded:

Two sequencing details are worth preserving alongside the timestamps. First, the EIN was obtained in the morning, before the Articles of Organization had been received that afternoon — the log records this as possible because the IRS’s registration step records a start month rather than an exact start date, so it did not require the Articles’ formal issuance timestamp to proceed. Second, the bank account application was begun at 1:44, before the 2:34 PM Articles arrived, but was not submitted until 3:14 PM, after them; the source leaves the application open across that gap rather than describing it as a continuous action.

Elapsed time, computed here from the timestamps above; the source does not state these as totals. From the Articles being received (2:34 PM) to bank approval (6:23 PM) is approximately three hours and forty-nine minutes. From the additional information being submitted (about 5:30 PM) to approval (6:23 PM) is approximately fifty-three minutes. From the initial filing (shortly after midnight) to approval (6:23 PM), the entire sequence falls within a single calendar day, well under twenty-four hours.

Privacy note. As part of opening the bank account, the applicant answered a set of identity-verification questions. Those questions asked about, in category rather than in answer: a description of the company’s business activity; a description of the specific product or service offered; external professional or social-profile links that could help verify the company or its owners; and the expected completion date of the company’s website, with whether a preview version existed. The applicant’s answers are not reproduced here, and are not otherwise summarized or paraphrased.

Relation to §11.3.3. The genesis process’s only stated duration is a design target, not a measurement: Stage 2 (Provisional Operations) is set at three to six weeks. This formation log describes an earlier and narrower slice of the process — the legal and financial mechanics that would sit at or before Stage 1 (Intent to Form), which itself carries no stated duration in §11.3.3 — and shows that slice completing within a single calendar day in this one instance. The two figures answer different questions and are not directly comparable: one is a multi-week target for an operations stage that follows formation, the other is a same-day measurement of formation itself.

11.7.2 A Three-Stage Model Presented to an External Audience

A separate document, dated by its own front matter to 2024-07-07, records how the model was described to an audience outside the network: a submission to Business Impact NW’s IMPACT Pitch 2024 competition. Because it was written to win a pitch rather than to specify a design, its claims are read here as what an applicant told a funding audience, not as a position the corpus otherwise adopts. This is the corpus’s only record of the model presented to an external audience in this form.

The document lays out a three-stage rollout with explicit calendar months attached — the only place in either source consulted for this section that ties a phased rollout to elapsed time rather than to headcount or milestone:

• Think Tank (Months 0–6): concept validation, model development, and educational content creation.
• Incubator (Months 7–12): supporting the formation of collaborative businesses, tracking adoption, customization, and early sustainability.
• Integration Services Provider (Months 13–18): measuring and scaling impact, including comparison against industry benchmarks and tracking of local economic effects.

Elsewhere in the same document, the same three stages are named “Think Tank,” “Incubation,” and “Integration,” without the month ranges attached — one document uses two slightly different namings for the same three-stage structure.

The document describes a single planned application meant to combine several functions into one flow: helping people find collaborators, providing education, running identity-verification checks, starting a new business, and managing an existing one — framed as comparable in ease to using an online banking application. That identity-verification step describes, at the level of a product concept, the same category of task that §11.7.1’s formation log documents as a manual, multi-hour exchange with a bank. The two records share a provide.io context but do not reference each other directly; the connection is drawn here as a plausible link between a stated product vision and a lived process, not as a fact either source states.

The pitch also describes a micro-learning feature grounded in behavioral science, aimed at skills including emotional intelligence, conflict resolution, leadership, and business management, delivered through game-like elements.

The document states an explicit rationale for using LLCs rather than cooperative or corporate structures for individual ventures: formation speed and legal portability across states. It is not the only place the corpus gives a reason for an LLC wrapper: docs/08-legal/01-modular-legal-forms.md lists “easy formation, broad use, member-managed options” as LLC strengths against limits including “not inherently cooperative, lacks embedded mission.” What is specific to this document is that the rationale is offered by an applicant to an outside audience rather than stated as design. §11.2 lists “Flexible Benefit LLC or Platform Cooperative” as alternative legal wrappers without stating a reason to choose between them.

On geographic focus, the document states an initial scope of proof-of-concept efforts that are remote or located in Portland, Oregon, continuing until judged viable by an unspecified vote. No further siting rationale is given, and the document does not define what the viability vote consists of.

11.7.3 A Single Instance, Not a Base Rate

Both records in this section describe one instance each: one measured formation process for one entity, one pitch document written for one audience at one point in time. Neither is a repeated or independently corroborated measurement. The corpus states durations elsewhere — §11.3’s three-to-six-week stage target, and feasibility and pilot windows in chapters 04, 06, and 13 — but those are design targets and planning assumptions rather than measurements, so none of them is a comparable against which either record here can be checked.

§11.3’s genesis process states a design target for one stage of onboarding without measuring it. §11.7.1 measures one instance of an earlier stage without stating a target for it. The two are complementary rather than substitutable: a target window states an expected duration for a designed process stage; a single timestamped log shows that a related, earlier legal and financial process completed within one day at least once. Neither can stand in for the other, and neither should be read as establishing what is typical. One same-day formation demonstrates that fast formation is possible; it does not establish an average, a rate, or a planning assumption the network can rely on. A larger, repeated sample of entity formations would be needed to state a typical duration for the legal and financial layer with any confidence.

The pitch document’s three-stage rollout (§11.7.2) sits on the same footing: it is a stated intention presented to a funding audience, not a measured outcome. Nothing in either source establishes that the Months 0–6 / 7–12 / 13–18 schedule was met.