Campaign-Business Operations and Open Technology Program Governance Policy

AI for Wisconsin / Five Letter Agency

Campaign-Business Operations and Open Technology Program Governance Policy

Korey Streich Campaign Committee and Five Letter Agency

Version 2.0.0 — July 25, 2026

AI for Wisconsin / Five Letter Agency — Open Technology Program Governance Policy

Contents

Document control, license, adoption, and publication architecture

Executive summary

Purpose, scope, and project model

Non-negotiable operating rules

Boundary architecture

Classification and decision framework

Full technology program, funding ceiling, and related-party contracting

Office, hardware, servers, providers, and shared infrastructure

AI agents, donor interactions, campaign operations, and program controls

Cost, contribution, obligation, and program classification

Open-source publication, licensing, contribution governance, and public audit

Public fundraising, Party Party revenue, sponsorship, advertising, subscriptions, and merchandise

KYN, platform governance, collective decision-making, and system amendments

Common scenario matrix

Mandatory operating policy for AI agents and human participants

Required workflows

Templates and minimum records

Stop and escalation triggers

Questions for Wisconsin Ethics Commission advice or qualified counsel review

Implementation and publication checklist

Source notes and authority hierarchy

Appendix A. One-page operating reference

Appendix B. Public program budget and milestone register

Appendix C. Transaction and program-ledger minimum schema

Appendix D. Open-source repository and release checklist

Appendix E. AI for Wisconsin implementation profile

Appendix F. Control registry summary

| AIWI-OPS-001 v2.0.0 | Public draft | July 25, 2026 | | | :---- | :---- |

AI for Wisconsin / Five Letter Agency — Open Technology Program Governance Policy
Policy ID: AIWI-OPS-001
Version: 2.0.0
Status: Public draft for adoption, open-source publication, treasurer approval, and campaign-finance review
Effective date: Not effective until adopted under Section 0.4
Last reviewed: July 25, 2026
SPDX-License-Identifier: CC-BY-4.0
Registered committee: Korey Streich Campaign Committee — Wisconsin Sunshine registrant 1148727

Important: This is a conservative operational policy and issue-spotting guide, not legal advice. Written Wisconsin Ethics Commission advice, qualified counsel, statutes, administrative rules, and later official guidance supersede it.

Version 2.0 supersession notice: This version replaces the earlier prototype-and-basic-hosting model. The controlling proposed program is now a $150,000 maximum campaign technology-program ceiling, including a prospective $72,000 fixed implementation ceiling for Five Letter Agency, up to $12,000 for twelve active months of managed operations, and $66,000 retained under Campaign Committee control for infrastructure/providers, independent review, pilots/community operations, and contingency. The fundraising ceiling is not an automatic expenditure and is not an entitlement to Five Letter Agency.

0. Document control, license, adoption, and publication architecture

0.1 Document control

0.2 Open-source/publication purpose

This policy is deliberately written as a public, forkable operating standard. Its goals are to:

make the campaign–vendor relationship inspectable rather than merely asserted;

let agents and humans apply the same controls from a versioned source;

allow other campaigns, civic projects, and vendors to adapt the framework;

expose budgets, milestones, authority boundaries, and audit methods without exposing protected records;

invite corrections and stronger controls through public issues and pull requests; and

preserve a clear line between public policy and confidential execution evidence.

The policy is open content. It does not grant rights to campaign or Party Party trademarks, private data, credentials, security secrets, or third-party copyrighted material. Software repositories, code, models, and hardware designs use their own explicit licenses.

0.3 Normative language and hierarchy

MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, and MAY have their ordinary standards meaning. Where documents conflict, the following hierarchy controls:

applicable law, binding orders, and written Wisconsin Ethics Commission advice;

signed campaign contracts and approved obligations, within law;

the latest formally adopted release of this policy;

adopted SOW schedules, data-processing terms, poll manifests, and runbooks;

machine-readable control registry generated from this policy;

examples, commentary, FAQs, website summaries, and agent memory.

A public contribution, model answer, GitHub issue, pull request, Discord statement, or community poll does not amend this policy until an authorized human adoption record identifies the exact version.

0.4 Adoption and effective date

This version becomes operational only after:

the candidate approves the policy’s project and transparency commitments;

the treasurer approves the financial, related-party, obligation, acceptance, and reporting controls;

FLA acknowledges the vendor, data, security, open-source, and transition obligations;

the campaign records any required external advice or counsel review;

the canonical public repository release is tagged and its digest recorded; and

restricted companion records and custodians are established without being committed publicly.

Until then, this is a planning and review draft. Adoption of the policy does not itself authorize a contract, expense, poll, deployment, data collection, or contribution acceptance.

0.5 Public source versus restricted companion records

0.6 Forking and adaptation profile

The portable rules are the main body of this policy. Campaign-specific values are isolated in Appendix E. A fork should replace the implementation profile, preserve attribution, state that it is modified, and avoid implying endorsement by AI for Wisconsin, the Korey Streich Campaign Committee, or Five Letter Agency. [S31]

0.7 How humans and agents use this policy

Start with Section 4. Identify the entity, program allocation, source, beneficiary, authority, data domains, and record location before taking action. Green means proceed with records; yellow means pause for the missing review/approval; red means reject or redesign.

Do not infer that fundraising progress authorizes spending. Every obligation and disbursement still needs its own authority.

Treat every Campaign Committee–FLA transaction as related-party, even while FLA is a sole proprietorship.

Record an obligation when the promise to purchase, rent, lease, or pay arises, not only when money moves. [S1][S3]

Use the public document for rules and the restricted companion register for sensitive evidence.

Open an issue or proposed patch when the policy is incomplete; do not improvise a hidden exception.

Executive summary

The new full-program model

The Campaign Committee may present one tangible, public technology goal: up to $150,000 to build, publish, launch, independently review, pilot, and operate the complete AI for Wisconsin open civic operating system during the campaign program period. The goal covers the public AI representative, Campaign Core, public web interfaces, Know Your Neighbor, auditable polling, infrastructure, open-source release, independent review, community pilots, managed operations, and a bounded contingency reserve. [S23][S29][S30]

The goal is a maximum program budget, not a representation that every dollar will be spent. It is also not a donor-restricted account unless the Committee lawfully establishes one. Public milestones explain intended results; the treasurer retains authority over actual obligations and disbursements.

Program allocation

Related-party rule

Five Letter Agency is owned by candidate Korey Streich. The Committee may purchase bona fide services from FLA only under a prospective, non-retroactive, milestone-based contract with a frozen baseline, pricing support, exact acceptance evidence, treasurer approval, public-safe disclosure, and required campaign-finance review. Earlier work is Background Material, volunteer activity, or separately analyzed in-kind value—not a backdated vendor debt.

No-upward-revision rule

The technology program’s public ceiling remains $150,000 for the defined campaign-period scope. New requirements must be handled by:

using an existing reserve;

reallocating uncommitted funds among program categories with a public amendment record;

replacing or deferring a lower-priority item;

reducing scope or service levels; or

treating the work as outside the campaign technology program.

No agent, public poll, vendor request, or informal commitment can raise the ceiling. A future governmental implementation, indefinite post-campaign operation, unlimited feature development, or unrelated Party Party/FLA commercialization is outside this goal.

Open-source/public accountability rule

The campaign publishes the policy, program budget, milestone definitions, accepted-deliverable summaries, payments, direct-cost categories, open-source releases, and material changes at an appropriate level. Protected donor information, KYN evidence, ballot selections, credentials, privileged advice, and exploit-enabling security details remain restricted. Openness is an accountability control, not permission to disclose sensitive data.

What supporters do and do not purchase

Contributions support the Committee’s lawful campaign program. They do not purchase:

a particular FLA invoice or guaranteed vendor payment;

additional ballots, weighted votes, or priority access;

KYN verification, credential status, or challenge immunity;

authority over campaign compliance, contracts, donor treatment, or official results;

access to private data or unreleased security findings; or

a future government contract or official decision.

Human authority

Hermes and other agents may prepare, validate, summarize, test, and execute narrowly approved deterministic workflows. They may not finally accept or refund contributions, bind contracts, approve related-party payments, set fair-market value, modify the public budget ceiling, adjudicate disputed identities, change open poll rules, publish an official tally from model arithmetic, or decide what protected material becomes public.

1. Purpose, scope, and project model

This policy operationalizes the organizational model established by the Know Your Neighbor investigation and the full technology funding plan: FLA/The Party Party operates or develops general civic technology and KYN; AI for Wisconsin is the campaign identity and operating system; the registered Campaign Committee controls campaign money, official campaign decisions, and campaign use of the platform; Campaign Core provides deterministic authority; and Party Favors or other rewards remain separate from identity, eligibility, credentials, and vote weight. [S23][S29][S30]

The purpose is not to conceal overlap. The overlap is public, contractually described, correctly valued, and divided across legal, financial, data, technical, and authority boundaries. Separate branding, domains, accounts, or code repositories do not excuse substance-based classification.

1.1 Defined organizational lanes

1.2 Program boundaries

The $150,000 goal covers the defined campaign-period technology program and up to twelve active months of managed operations. It does not cover indefinite operation, a post-election State of Wisconsin system, unlimited amendments, unrelated FLA products, general Party Party commerce, personal expenses, or a guaranteed enterprise service level.

1.3 Controlling cost test

Core test: Does the expense, service, asset, or obligation exist because of campaign activity, fall within an adopted program category, and have a campaign portion that can be specifically demonstrated?

If it would exist anyway and the campaign portion is only a predicted share of a mixed flat cost, the campaign should not pay it without written advice. Wisconsin’s published 2025 opinion rejected a proposed mixed allocation for a computer and flat cell-phone plan that would exist regardless of the campaign, while contrasting those costs with traceable mileage. [S9]

2. Non-negotiable operating rules

3. Boundary architecture

3.1 Recommended money flow

3.2 Program funds do not flow automatically

The $150,000 public goal is held and controlled by the Campaign Committee. No donor contribution is automatically assigned to FLA. FLA’s maximum proposed compensation is limited to accepted implementation milestones and activated operations months. Infrastructure, review, pilot, and contingency allocations remain Committee-controlled unless separately and prospectively obligated.

3.3 Prohibited or presumptively unsafe flow

A corporation or other prohibited source pays FLA to build or operate a campaign-specific asset and the campaign receives the benefit without lawful Committee payment or contribution treatment.

A Party Party Patreon tier says that business payments finance official campaign infrastructure while bypassing the campaign contribution system.

The Committee transfers a lump sum to FLA because the fundraising goal was reached, without accepted deliverables or service periods.

FLA is paid from the independent-review reserve to review its own work or choose a reviewer whose independence is compromised.

The Committee reimburses FLA’s general office, home, Internet, utilities, mixed hardware, or unrelated subscriptions through estimated percentages.

A sponsor, donor, customer, or patron receives campaign policy control, KYN assurance, ballot weight, or official decision rights because of payment.

Donor, KYN, ballot, or Party Party customer data is joined for fundraising, advertising, or political profiling without a separately approved lawful purpose.

A foreign national directs campaign budgets, fundraising, messaging, donor administration, official poll rules, or campaign-specific deployment priorities. [S14]

4. Classification and decision framework

4.1 Eight-question decision tree

4.2 Risk labels

5. Full technology program, funding ceiling, and related-party contracting

5.1 The Committee’s public program ceiling

The Campaign Committee may solicit contributions toward a maximum $150,000 AI for Wisconsin technology program. The program is defined by the Funding Plan, the full-system SOW, this policy, and the adopted technical requirements. [S23][S29][S30]

The ceiling is intentionally broad enough to avoid repeatedly raising the public technology target. It covers the defined campaign-period system, reviews, pilots, direct costs, operations, and contingency; it does not promise unlimited work.

5.2 Program allocation and control

Unspent or uncommitted allocations remain Campaign Committee funds and do not become FLA property. Reallocation requires a public-safe amendment record and may not evade campaign-finance, acceptance, or related-party controls.

5.3 FLA fixed implementation ceiling and milestones

The proposed FLA implementation ceiling is $72,000, paid only through accepted milestones:

A milestone may be subdivided only if the total does not increase and every payment remains tied to an independently useful accepted deliverable.

5.4 Managed operations ceiling

The Committee may activate up to twelve service months at $1,000 per active month, maximum $12,000. The service includes only the approved service inventory: website and agent serving, routine health/alert review, deployments, DNS/TLS, backups, maintenance, credential-expiration support, incident triage, monthly operations reporting, and orderly transition.

No fee accrues before the written activation date, during an authorized full suspension, after termination/transition, or for a month in which the material service inventory was not delivered. The service is not a 24/7 staffed enterprise SLA, unlimited development retainer, or guarantee of uptime.

5.5 Committee-held reserves

Infrastructure/provider reserve: Prefer Committee-owned accounts and assets. Pay actual documented campaign costs; no hidden markup or guessed share of FLA overhead.

Independent-review reserve: Contract directly where practical. FLA may provide evidence and remediation but does not control conclusions.

Pilot/community reserve: No payment for a vote, political answer, credential approval, or favorable review. Participant reimbursement or support must use neutral published rules.

Contingency/amendment reserve: Every use requires a written trigger, exact scope, cost, source, authority/privacy/security impact, acceptance evidence, and public-safe summary.

5.6 Non-retroactive baseline

Development began before the proposed full-system contract. The parties therefore MUST:

freeze exact repository commits, deployed artifact digests, provider accounts, hardware, and implementation status immediately before financial effectiveness;

classify existing material as Background Material/Background IP, campaign data, third-party material, or restricted configuration;

state that no pre-effective labor or cost becomes payable under the prospective SOW;

have the treasurer separately determine whether earlier campaign-specific benefit was volunteer activity or authorized/reportable in-kind support;

replace any milestone already substantially complete with additional prospective deliverables of equivalent approved value or reduce the fee; and

publish a public-safe baseline summary without exposing secrets or private campaign records.

5.7 Mandatory related-party packet

5.8 Valid patterns

5.9 Invalid or redesign-required patterns

Paying FLA all or a percentage of the $150,000 merely because funds were raised.

Paying an unaccepted milestone, a service month not activated/delivered, or work materially complete before the contract baseline.

Using the review, pilot, direct-cost, or contingency reserves as an undisclosed increase to FLA compensation.

Paying FLA’s ordinary office, home, utilities, mixed hardware, general product roadmap, Party Party commerce, or personal living costs.

Letting FLA forgive debt, offer nonordinary terms, or leave obligations unresolved without contribution/credit review.

Accepting a patron/sponsor earmark for campaign-specific infrastructure outside the campaign contribution lane.

Treating an open-source label as proof that pricing, source eligibility, data handling, or campaign purpose no longer matters.

5.10 No-upward-revision and amendment procedure

A proposed change must state:

the exact added, removed, or substituted requirement;

the allocation and remaining capacity;

whether FLA or another vendor will perform it;

price and source support;

authority, privacy, security, legal, accessibility, and operations impact;

acceptance evidence; and

public disclosure effect.

If the change cannot fit within existing uncommitted allocations, the Committee defers or substitutes work rather than increasing the public technology ceiling. A platform poll may recommend an amendment but cannot create an obligation or deploy code automatically.

6. Office, hardware, servers, providers, and shared infrastructure

6.1 Dedicated commercial campaign space

A dedicated area in a commercial FLA office can be structured as a campaign expense more credibly than a rough share of a mixed workspace. Because no published Wisconsin decision located here directly approves candidate-owned office rent, the first lease or charge is a YELLOW item for a confidential Commission request. [S12]

Use a written sublease or license and confirm that FLA's underlying lease permits it.

Define the exact room, square footage, furniture, storage, access, dates, and campaign-only use.

Support the rate with local commercial comparables or the proportionate amount FLA actually pays for the dedicated area, without a candidate-benefit markup.

Keep a floor plan, photographs, access list, and use log.

Separate campaign Internet, phone, printing, security, and other services when feasible; otherwise charge only actual measurable campaign increments.

The Campaign Committee should pay FLA under ordinary terms and report the obligation and payments with a specific purpose.

6.2 Shared FLA office

Internal rule: Do not charge a predicted percentage of FLA's flat lease, utilities, Internet, or general office overhead merely because campaign work sometimes occurs there. Dedicate a measurable unit, charge a documented per-use room rate offered on ordinary terms, treat the candidate's personal provision as a properly analyzed contribution, or obtain written advice.

This conservative rule follows the Commission's distinction between traceable campaign mileage and flat mixed-use costs that would exist anyway. [S9]

6.3 Residence and household costs

Campaign funds should not pay mortgage, home rent, household utilities, general home Internet, repairs, or ordinary household equipment. Wisconsin's personal-use rule and 2025 opinion create substantial risk. Federal guidance expressly bars a federal campaign from renting space in the candidate's home; that is an analogy, but it supports the conservative internal rule. [S8][S9][S15]

A campaign meeting at a residence does not convert the residence into reimbursable office space. Document event-specific costs separately where clearly allowed; do not allocate the home itself.

6.4 Raspberry Pi 5, OptiPlex, networking, and storage

6.5 Asset ownership and end-of-use

Campaign-purchased equipment belongs to the Campaign Committee, not automatically to KC or FLA.

FLA-owned equipment remains FLA property unless sold or contributed under a documented transfer.

Do not move campaign assets into FLA after the campaign without a lawful fair-market sale, permitted disposition, or other reviewed process.

Maintain serial number, purchase date, payer, custodian, location, use restriction, and disposition record for every material asset.

6.6 Program asset and provider register

Every asset/provider funded from the technology program records: owner; payer; custodian; allocation code; purchase/obligation date; campaign purpose; data classes; credentials owner; physical/logical location; replacement and warranty; depreciation/tax treatment for review; backup/restore role; public-disclosure level; and exit/disposition plan.

Committee-owned accounts are preferred for domains, campaign email, messaging, hosting, payment processing, public analytics, and campaign-specific provider services. Where FLA must hold a master account, the SOW identifies the campaign tenant, actual charges, export rights, credential transition, and termination procedure.

7. AI agents, donor interactions, campaign operations, and program controls

7.1 Four permissible classification lanes

7.2 What the agent may do under an approved campaign workflow

Draft donor, volunteer, press, constituent, or event communications for human review.

Answer approved factual FAQs using a versioned knowledge base and display the required campaign attribution where applicable.

Summarize inbound messages and suggest routing, without making a legal donor determination.

Schedule approved communications and reminders after a human approves content, audience, sender, and entity.

Prepare a proposed campaign-finance ledger entry from an invoice or receipt, while flagging uncertainty for the treasurer.

Calculate metered API, SMS, email, compute, or hosting usage from deterministic logs.

Generate draft KYN poll manifests, explanations, or reports; deterministic services and authorized humans must approve eligibility, sponsorship, timing, and results.

Send standardized contribution acknowledgements only after the payment processor and treasurer-controlled rules mark the contribution accepted.

7.3 Actions requiring human approval

7.4 Prohibited autonomous agent actions

Do not invent a donor's citizenship, residence, employer, identity, or source-of-funds status.

Do not split, reroute, rename, or disguise contributions to make them appear permissible.

Do not send money, issue refunds, sign contracts, approve invoices, or change bank/payment settings.

Do not promise a sponsor, patron, donor, or contributor policy access, governance authority, KYN status, or voting advantage.

Do not merge campaign donor records, Party Party customer records, KYN identity evidence, or secret ballots.

Do not let a foreign national or unauthorized person approve election-related budgets, messaging, fundraising, poll administration, or campaign operations. [S14]

Do not publish an official poll result from a language-model calculation; use deterministic tally code and signed audit artifacts.

Do not generate or deploy campaign communications without the correct entity attribution and, when applicable, Wisconsin synthetic-media notice. [S11][S13]

Do not launch automated outbound email, SMS, voice, or direct-message campaigns until a separate channel-specific review confirms consent, identification, opt-out, platform, and recordkeeping requirements.

7.5 Donor interaction examples

7.6 AI-generated political audio and video

Wisconsin requires prescribed disclosures for certain audio or video political or issue advocacy substantially produced with generative AI. Audio must include 'Contains content generated by AI' at the beginning and end; synthetic portions of video require the applicable continuous written disclosure. These are separate from ordinary campaign attribution requirements. Use deterministic publication templates; do not rely on Hermes to remember the notice. [S13]

7.7 Technology-program actions

Agents MAY prepare budget-status summaries, milestone checklists, invoice comparisons, provider-cost reconciliations, release manifests, and public transparency drafts from authoritative records. Agents MUST NOT:

infer that available cash or fundraising progress authorizes spending;

approve an FLA milestone or monthly operations invoice;

move funds among program categories without an adopted amendment;

select an “independent” reviewer whose independence has not been human-confirmed;

conceal a budget variance, failed test, rejected deliverable, incident, or reserve draw;

publish donor identities or other protected records as part of transparency reporting; or

represent a planned, coded, tested, deployed, or accepted feature as another status.

8. Cost, contribution, obligation, and program classification

8.1 Required internal codes

8.2 What must be captured

The internal ledger records every contribution, disbursement, obligation, direct cost, in-kind benefit, credit, refund, debt change, program reallocation, and reserve draw regardless of current filing status. [S3][S17]

At minimum capture:

obligation date, payment date, payee, address, exact purpose, amount, allocation code, and reporting status;

SOW milestone or service month, acceptance status, reviewer, defects, credits, and artifacts;

provider invoice, actual metering, ownership, account, and data/security classification;

fair-market support for in-kind or discounted benefits outside a statutory exclusion;

candidate personal funds/property contributed to the Committee; [S4]

remaining category capacity and total uncommitted technology-program capacity;

public-disclosure record or reason for lawful/security/privacy withholding; and

correction history without erasing the prior record.

8.3 Subscriptions and API plans

8.4 No marginal cost does not mean no value

A commercial agent or hosting service can have value through software, configuration, data, operator responsibility, reliability, security, and support even when the next API call costs little. Conversely, qualifying uncompensated individual Internet activity may be excluded under Wisconsin law. Classification follows facts and law, not a blanket zero-cost assertion. [S1][S5]

8.5 Fundraising progress and program accounting

The campaign SHOULD publish a public-safe technology ledger showing, at minimum: goal; contributions to the Committee in aggregate as appropriate; obligations; paid amounts; category commitments; uncommitted balances; milestone status; accepted releases; direct-cost categories; review/pilot status; reserve draws; credits/refunds; and final unused-fund disposition. The public ledger is not the official campaign-finance filing and must not expose nonpublic donor data.

8.6 Limited-activity reporting exemption

An exemption does not erase activity. Contributions, disbursements, debts, obligations, and candidate funds count toward the threshold. The $150,000 program and any related contract require active monitoring and likely make reliance on a limited-activity posture inappropriate once obligations/activity exceed the applicable threshold. [S17]

9. Open-source publication, licensing, contribution governance, and public audit

9.1 Publication policy

Public source is the preferred default for policy, architecture, schemas, deterministic rules, tests, deployment recipes, public-verification tools, hardware designs, accepted prompts/templates, dependency manifests, and public-safe audit evidence. The objective is reproducibility and scrutiny, not disclosure of secrets or participant data.

9.2 License model

This policy text, templates, and companion control files are licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). The license permits sharing and adaptation, including commercial use, with attribution and indication of changes. [S31]

Software, schemas treated as software, hardware designs, model artifacts, fonts, media, datasets, and third-party components use separate repository-level licenses and notices.

Trademarks, campaign names/logos, Party Party branding, personal likenesses, private data, credentials, and third-party rights are not granted merely because a document is public.

A LICENSE, NOTICE, dependency/SBOM record, and per-repository license policy MUST accompany public releases.

9.3 Canonical repository and release integrity

The canonical policy repository SHOULD contain:

/policy/AIWI-OPS-001.md
/policy/implementation-profile.yaml
/policy/controls.yaml
/policy/CHANGELOG.md
/policy/ADOPTION.md
/LICENSE
/NOTICE
/CONTRIBUTING.md
/SECURITY.md
/CODE_OF_CONDUCT.md

Each adopted release records: semantic version; commit hash; content digest; adoption authorities; effective date; superseded version; source review date; public/restricted change classification; and links to applicable SOW/budget/poll manifests.

9.4 Normative versus informative content

The policy body and machine-readable controls are normative after adoption. Source notes, examples, FAQs, public summaries, diagrams, and implementation commentary are informative unless expressly incorporated. A website rendering or translated copy must identify the canonical version and disclose translation status.

9.5 Contribution workflow

Contributor opens an issue or pull request against the public source.

Maintainer labels the change: editorial, operational, financial, legal/compliance, security/privacy, KYN/polling, accessibility, or campaign-specific.

Automated checks validate formatting, links, control IDs, profile schema, and consistency.

Human reviewers evaluate substance. Legal/financial changes require candidate/treasurer and applicable external review; security/privacy changes require assigned reviewers.

Campaign-specific deployment or adoption is performed only by eligible authorized campaign humans.

Accepted change receives a changelog entry, release tag, adoption record, and public digest.

Rejected or deferred changes remain visible with reasons when safe.

Public contribution does not create vendor status, compensation, a campaign role, KYN assurance, governance weight, or a right to deployment.

9.6 Foreign-national and open technical contribution boundary

International contributors may participate in generic open-source discussion and reusable technical work, subject to applicable law and project rules. They must not direct campaign budgets, fundraising, messaging, donor administration, official campaign poll rules, campaign-specific expenditures, or other election-related decision-making. [S14]

Campaign-sensitive issues MUST be labeled and merged/deployed only by authorized eligible persons. Any uncompensated campaign-specific contribution from a source whose eligibility is uncertain is placed on review hold.

9.7 Security reporting and responsible disclosure

Do not open a public issue containing credentials, personal data, active exploit instructions, exact sensitive topology, or a vulnerability that materially endangers a live system. The public repository SHALL include a private security-reporting method. The project publishes a public-safe advisory after containment, affected-version analysis, remediation, and disclosure review.

Security transparency includes controls, threat models, audit scope, affected versions, and remediation status. It does not require releasing live secrets or a weaponized exploit before users are protected.

9.8 Public/restricted release gate

Before publication, every artifact is classified:

PUBLIC_APPROVED

PUBLIC_REDACTED

EMBARGOED_SECURITY

RESTRICTED_CAMPAIGN

RESTRICTED_DONOR

RESTRICTED_KYN_IDENTITY

RESTRICTED_BALLOT

PRIVILEGED_LEGAL

THIRD_PARTY_RESTRICTED

An AI model may propose the classification but cannot be the sole release authority.

9.9 Open-source funding and campaign accounting

The campaign may lawfully commission a public release as a campaign deliverable when the purpose, scope, price, rights, baseline, and acceptance evidence are documented. Public availability does not make engineering or operations free, and it does not authorize the Committee to pay for unrelated FLA product development.

Community contributions reduce neither the need to classify campaign-specific benefit nor the value of FLA deployment, support, data, and operations work. Discounts or donated campaign-specific work remain subject to source and contribution analysis.

9.10 Forks, modifications, and non-endorsement

A fork must preserve attribution, state material changes, replace the implementation profile, and avoid suggesting that the original project endorses the fork. Official AI for Wisconsin policy is only the exact adopted canonical release identified by the Campaign Committee.

10. Public fundraising, Party Party revenue, sponsorship, advertising, subscriptions, and merchandise

10.1 Campaign technology-program solicitation

The Campaign Committee may describe the $150,000 ceiling as a tangible program goal using the adopted funding plan. Public language MUST state:

contributions are made to the Korey Streich Campaign Committee;

the goal is a maximum budget, not an automatic expenditure;

FLA is a candidate-owned related-party vendor;

FLA’s proposed ceilings are $72,000 implementation and $12,000 managed operations;

$66,000 remains Committee-controlled for direct costs, review, pilots, and contingency;

no donation purchases votes, credentials, data access, policy control, or vendor entitlement; and

actual spending remains subject to treasurer approval, legal/source rules, milestone/service acceptance, and public-safe reporting.

Suggested concise language:

Help build Wisconsin’s open-source AI-governance prototype. AI for Wisconsin is raising up to $150,000 to build and operate a public AI representative, transparent campaign operating system, privacy-preserving KYN identity and credential service, auditable local and statewide polling, reproducible infrastructure, public verification tools, and independent legal, security, privacy, cryptographic, and accessibility review. The goal is a ceiling, not an automatic expenditure. Five Letter Agency, owned by candidate Korey Streich, may be paid only under a prospective milestone-based agreement approved through campaign controls. Donations do not buy votes, credentials, platform authority, private data, or influence over official tallies.

10.2 Cumulative public milestones

These are program priorities, not donor-purchased features or automatically restricted subaccounts. Security and legal gates may change sequencing while the public ceiling remains fixed.

10.3 Party Party/FLA business-revenue lane

FLA/The Party Party may receive ordinary business revenue for general media, civic technology, memberships, merchandise, advertising, sponsorship inventory, education, events, and noncampaign clients. The solicitation and actual use must not earmark the money for campaign-specific infrastructure, communications, staff, polls, donor operations, or official campaign decisions.

Safer business wording: Membership supports The Party Party’s media, open civic-technology, education, and community work. It is not a contribution to the candidate committee and does not provide voting power, KYN status, campaign access, or official decision authority.

Unsafe wording: Fund the AI for Wisconsin campaign’s official Hermes, KYN, polling, or campaign server through this Patreon or corporate sponsor package.

10.4 Earmarking and actual use

A disclaimer cannot cure contradictory conduct. If FLA solicits or accepts money specifically to provide a campaign asset, the campaign benefit must be handled through a lawful campaign purchase, permissible volunteer activity, or authorized in-kind contribution. Corporate and foreign sources present particular risk. [S10][S14][S33]

Do not promise that a Party Party subscription percentage will finance the Committee unless a lawful, sourced, recorded transfer is separately established.

Do not use sponsor money to satisfy an FLA campaign milestone or operations month when the sponsor earmarked it for the campaign.

A general sponsor may support a public reusable release only under neutral terms with campaign-specific work separated.

The Committee’s later purchase from FLA must stand on its own contract and price, not a hidden sponsor subsidy.

10.5 Sponsorship and advertising

10.6 Merchandise and subscriptions

Party Party-branded merchandise and commercial memberships belong to FLA’s lane.

Candidate/campaign-branded merchandise ordinarily belongs in the Campaign Committee fundraising lane.

Dual branding requires prospective ownership, inventory, fulfillment, IP/license, revenue, and campaign-benefit allocation.

Purchases/subscriptions never affect KYN, ballots, credentials, review priority, or campaign authority.

Applicable seller-permit, sales-tax, income-tax, and information-return duties require separate tax review. [S21][S22][S24]

10.7 Required system separation

11. KYN, platform governance, collective decision-making, and system amendments

11.1 Four decision classes

11.2 No payment-based governance

Patronage may unlock commercial content, recognition, non-governance community features, or a voice in Party Party product feedback. It must not produce more votes, weighted votes, higher KYN assurance, priority credential review, immunity from challenge, privileged official campaign access, or a stronger claim on public decisions. The KYN design and this technology program require separation of identity, polling, rewards, commercial support, and campaign finance. [S23][S29]

11.3 Polls about changing the system

A platform-amendment poll must declare who is eligible, whether the result is advisory or binding within the project, quorum, separate constituencies, implementation review, and effective date.

A passed poll creates an implementation proposal, not an automatic code deployment or legal act.

Security, privacy, source eligibility, campaign law, and system integrity constraints cannot be bypassed by a simple majority.

Campaign adoption of a KYN platform amendment is a separate authorized campaign decision when the change affects campaign operations.

Paid status and campaign contribution history are never eligibility claims for civic governance.

11.4 Offloading KC's personal decisions

A public or patron-assisted decision system for KC's personal or creative choices can be part of Party Party media, provided the facts remain honest: the decision is personal/business, payments do not buy official influence, campaign resources and donor data are not used, and any costs are paid personally or by FLA. If the question becomes how campaign money is spent, how donations are solicited, what a campaign contract promises, or how official campaign systems operate, it moves into the campaign class and requires authorized human control.

11.5 If elected

The boundary becomes more demanding if KC assumes public office. Wisconsin's ethics guidance says state officials should not act officially in privately interested matters, use public position for private benefit, exchange influence for contributions, or use confidential information to receive value. State candidates and officials disclose employers, investments, commercial clients, associated organizations, real estate, and creditors through Statements of Economic Interests. [S19][S20]

Prepare a pre-office conflict and recusal policy for FLA, Party Party, KYN, sponsors, clients, and licensees.

Do not let a Party Party/KYN vote direct an official action where FLA or an associated organization has a financial interest without ethics review and appropriate recusal/authority controls.

Do not use public resources, nonpublic government data, staff, branding, or procurement to enrich FLA or patrons.

Consider independent governance, divestment, licensing at public/nonpreferential terms, or operational separation before inauguration.

11.6 Technology-budget and amendment polls

A public poll may recommend priorities or reallocations within the adopted $150,000 ceiling. It may not:

accept or spend campaign money;

bind the treasurer to an unlawful or unsupported transaction;

award work to FLA or another vendor automatically;

waive related-party, source, privacy, security, accessibility, or acceptance controls;

increase the public ceiling; or

convert donor/patron status into eligibility or weight.

A passed recommendation becomes a versioned change proposal. Authorized humans determine legality, available allocation, contracting, implementation, testing, and release; the disposition is published with reasons.

12. Common scenario matrix

13. Mandatory operating policy for AI agents and human participants

13.1 Agent system instruction

MUST: Before taking or recommending any action involving money, services, infrastructure, data, public communications, polling, donors, patrons, sponsors, or FLA, identify the responsible entity, campaign purpose, cost classification, source eligibility, required human approver, and record location.

MUST NOT: An agent must not execute a payment, refund, contract, contribution acceptance, reporting classification, related-party approval, sponsor commitment, data merge, official poll change, credential adjudication, or campaign-sensitive deployment without explicit authorized human approval.

13.2 Agent authority matrix

13.3 Required agent log fields

13.4 Required agent escalation phrases

'This is a related-party Campaign Committee-to-FLA transaction. I have placed it on LEGAL_REVIEW_HOLD pending a written SOW, fair-market support, treasurer approval, and the applicable advisory decision.'

'This appears to be a mixed flat-rate cost that cannot presently be tied to actual campaign use. The campaign should not pay the proposed allocation.'

'This sponsor/patron payment is described as financing campaign-specific activity. It cannot be accepted through the FLA lane without campaign-finance review.'

'I cannot determine donor/source eligibility from the available facts. The payment must remain held for an authorized human review.'

'This proposed patron benefit would change voting, KYN, or campaign decision power. The feature is prohibited by project policy.'

'This contributor may be a foreign national or is participating in campaign-specific decision-making. The task is blocked pending eligibility review.'

13.5 Additional program-control log fields

13.6 Public-source rule for agents

An agent SHALL cite the canonical policy/control version used for a consequential recommendation. If its available policy is stale, conflicting, unofficial, or missing a required profile value, it must stop execution, state the discrepancy, and request human resolution. Agent memory and conversation history never supersede the adopted repository.

14. Required workflows

14.1 Adopt or amend this public policy

Open a versioned public change with rationale and affected controls.

Classify financial, legal, security/privacy, KYN/polling, accessibility, campaign-specific, and restricted impacts.

Obtain required human and external review.

Update policy, implementation profile, machine-readable controls, changelog, and public/restricted migration notes.

Candidate and treasurer adopt the exact commit/tag as applicable.

Publish the release manifest and effective date.

Update agents and services; verify stale versions fail closed for protected operations.

14.2 Campaign purchase from FLA

Create a campaign need/change statement tied to the adopted program and allocation.

Confirm the frozen baseline and that the deliverable is prospective.

FLA prepares the milestone/service packet, pricing support, data/security/IP effects, and invoice draft.

Independent reviewer verifies evidence; candidate may confirm technical facts but is not sole financial approver.

Treasurer reviews purpose, source, conflict, price, allocation, obligation/reporting, and advice conditions.

Record obligation before execution where required.

FLA delivers; reviewer records acceptance/rejection/conditions.

Treasurer authorizes payment only within accepted amount and allocation.

Publish public-safe scope, status, amount, evidence digest, and credits; retain protected packet privately.

14.3 Implementation milestone acceptance

Verify required acceptance package against Schedule F.

Confirm code/artifact/policy/model/dependency versions and environment.

Run required tests, negative paths, security/privacy checks, accessibility journeys, and restore/audit verification.

Identify defects, exceptions, residual risk, and whether deliverable is independently useful.

Record ACCEPTED, CONDITIONALLY_ACCEPTED, REJECTED, or SUPERSEDED.

Payment may not exceed the accepted value; rejected/uncured work is not due.

14.4 Managed operations month

Treasurer activates exact service inventory and month.

FLA operates only authorized services/accounts/data.

FLA records availability, deployments, backup/restore status, incidents, security maintenance, direct costs, and unresolved risks.

Committee verifies material service delivery and any credits/suspension.

Treasurer accepts and pays up to $1,000 for the active month.

Publish monthly public-safe operations summary.

14.5 Direct infrastructure/provider purchase

Identify asset/provider, campaign purpose, allocation, owner, account, data class, and exit plan.

Prefer Committee ownership and direct payment.

Obtain prospective approval and provider invoice/terms.

Inventory asset/account, credentials custodian, backup/retention, and public-disclosure level.

Reconcile actual cost; no guessed FLA overhead or hidden markup.

14.6 Independent review

Committee defines scope and selects reviewer independently of FLA.

Reviewer discloses conflicts, methodology, deliverables, access, confidentiality, and publication plan.

Committee contracts/pays from review allocation where practical.

FLA supplies evidence but cannot edit conclusions.

Findings receive severity, owner, remediation, retest, and public-safe summary.

14.7 Contingency or system amendment

Record trigger and why existing scope/allocation is insufficient.

Define exact change, price, source, vendor, risks, removed/substituted work, and remaining capacity.

Obtain technical, privacy/security, legal/financial, and accessibility review as applicable.

Treasurer approves written change order inside the $150,000 ceiling.

Implement/test/accept; publish public-safe amendment and budget effect.

14.8 Volunteer or in-kind service

Identify person/source, activity, dates, campaign specificity, and compensation.

Determine whether a statutory volunteer/Internet exclusion applies or whether the benefit is in-kind.

For a clear exclusion, document facts and no-specific-compensation representation.

For in-kind support, obtain prior consent, written details, fair-market value, attribution, and campaign record. [S6][S7]

Do not use volunteer classification to evade an FLA milestone, paid worker, or prohibited source.

14.9 Sponsor/patron intake

Record payer/entity, country/source indicators, amount, requested benefits, and restrictions.

Ask whether funds are earmarked for campaign assets, messages, staff, polls, donor systems, FLA milestones, operations, or election-related decisions.

If yes/ambiguous, hold and do not accept through the business lane.

Match lawful business sponsors to published Party Party inventory/rates.

Prohibit campaign/KYN/ballot/data/governance privileges.

If campaign later purchases a service, use a separate ordinary campaign contract without sponsor earmark.

14.10 Open-source release

Inventory source, licenses, Background IP, dependencies, secrets, data, security findings, and campaign-specific configuration.

Run secret/PII/license/security scans and reproducible build/tests.

Classify each artifact public/restricted.

Approve public release, tag commit, generate SBOM/release manifest/digest, and publish docs/verifier tools.

Archive restricted release evidence and record public correction/security-reporting process.

14.11 Shared infrastructure

Identify owner, payer, administrator, tenants, allocation, and data classes.

Create separate identities, networks, databases, keys, backups, logs, and access lists where required.

Classify as dedicated, metered, managed service, volunteer/in-kind, or unallocable mixed cost.

Do not allocate flat cost by prediction.

Establish incident, restore, export, termination, and asset-disposition procedures.

Review quarterly and upon material use/entity change.

15. Templates and minimum records

15.1 Related-party full-system SOW

Must identify: exact parties; campaign purpose; non-retroactive baseline; full workstreams; milestone ceiling/schedule; operations ceiling/service inventory; Committee-held reserves; direct-cost rules; exclusions; acceptance; conflict/independent review; data/security/privacy; IP/licenses; public release; transition; termination; conditions precedent; and signatures.

15.2 Milestone delivery and acceptance packet

milestone ID, scope, amount, obligation reference, baseline, and delivery date;

exact code/artifact/policy/model/dependency versions and digests;

acceptance criteria and evidence index;

test/security/privacy/accessibility/restore/audit results;

known defects, exceptions, residual risks, and remediation;

public/restricted classification;

technical reviewer decision;

treasurer financial acceptance/payment decision; and

public-safe milestone summary URL/digest.

15.3 Monthly operations record

active service month and inventory;

service availability/interruptions;

deployments and changes;

backup age, restore verification, certificate/credential status;

incidents, containment, remediation, and disclosure status;

direct provider costs and credits;

unresolved risks and recommended changes;

service acceptance/credit; and

public-safe operations summary.

15.4 Invoice

Include invoice number/date, exact parties/addresses, SOW and obligation reference, milestone/service period, specific purpose, accepted amount, actual approved direct costs with evidence, credits, prior payments, remaining balance, allocation code, and certification that no personal/FLA-only or pre-effective costs are included.

15.5 Public technology-program ledger record

Include: program version; $150,000 ceiling; category maximums; obligations/payments/credits; uncommitted balances; milestone/service status; direct-cost categories; review/pilot status; reserve draws; release/audit links; public-withholding reason; and correction history.

15.6 Public release manifest

Include: policy/repository/release identifiers; commit/digest; license/NOTICE; SBOM; build/test evidence; adoption/approval; data/security classification; known limitations; superseded release; and verification instructions.

15.7 Restricted companion register

Record protected artifact ID, classification, purpose, custodian, authorized roles, encryption/key boundary, retention, backup, legal hold, deletion, public summary, and audit access. Never place raw secrets or protected data in the public policy repository.

15.8 Organizational transfer record

Whenever FLA/KYN work, data, account, asset, or infrastructure becomes campaign-controlled, record source/destination, exact asset/service/data, purpose, rights, value/payment or in-kind treatment, source eligibility, approver, security/privacy review, export/termination, and public disclosure.

15.9 Sample disclosures

Program relationship: AI for Wisconsin is operated through the Korey Streich Campaign Committee. Five Letter Agency, owned by candidate Korey Streich, is a disclosed related-party technical vendor. The Committee’s $150,000 technology goal is a maximum program budget, not an automatic payment to Five Letter Agency. FLA may receive up to $72,000 for accepted implementation milestones and up to $12,000 for activated managed operations; other funds remain Committee-controlled for direct costs, independent review, pilots, and contingency.

Party Party relationship: The Party Party is a commercial media and civic-technology project operated through Five Letter Agency. Payments to The Party Party are not campaign contributions and do not provide KYN status, civic votes, campaign policy authority, or preferential access to official decisions.

Leaving-site notice: You are leaving a Campaign Committee website and entering a separately operated Five Letter Agency/The Party Party service. Payments there are not contributions to the Korey Streich Campaign Committee.

KYN poll disclosure: Operator: [exact KYN operator]. Sponsor: [exact organization]. Funding source: [Committee payment / FLA general civic program / other]. Participation is free. Donation, purchase, subscription, patron, Party Favors, and engagement status do not change eligibility or vote weight. Poll class: [open sentiment / verified nonrepresentative consultation / advisory / determining within stated project authority].

16. Stop and escalation triggers

17. Questions for Wisconsin Ethics Commission advice or qualified counsel review

The Commission accepts requests about matters to which the requestor is or may become a party, and written requests/replies are confidential unless the requestor makes them public. [S12] The request should provide the exact facts, registered committee, FLA sole-proprietor status, full funding plan/SOW, baseline procedure, milestone schedule, operations model, open-source plan, infrastructure facts, and disclosures.

May the Campaign Committee purchase the described full open civic operating system, KYN, polling, website, infrastructure, open-source release, and managed operations from the candidate’s sole proprietorship under the proposed milestone/acceptance/conflict controls?

Is the proposed $72,000 fixed implementation ceiling and $12,000 operations ceiling appropriately structured, and what additional fair-market, reporting, or approval evidence should be maintained?

How should pre-effective development be classified when the contract pays only for prospectively defined remaining/replacement deliverables?

How should the Committee report obligations and milestone payments, including a milestone partly rejected, reduced, credited, or replaced?

May the Committee publicly solicit toward a $150,000 technology-program ceiling using the proposed allocation/milestone language, and what additional disclaimer or attribution is required?

What valuation/reporting method applies when campaign-funded work is released under a public license and FLA or others may reuse it?

How should campaign-specific hosting/API/provider use inside an FLA master account be valued when actual usage is metered, and when should accounts be Committee-owned?

May the Committee purchase a managed service running on FLA-owned general infrastructure without separately reimbursing mixed hardware/office/Internet costs?

May the Committee rent a specifically defined campaign-only nonresidential area controlled by FLA, and what documentation is required?

How does the individual Internet-activity exclusion apply to KC’s own uncompensated use of existing agent tools, and when does the activity become an FLA vendor service or in-kind contribution?

How should free/discounted KYN service, community contributions, or generic open-source work be treated when the campaign receives a campaign-specific benefit?

What controls are required when Party Party receives subscriptions/sponsorships while FLA separately contracts with the Campaign Committee?

What attribution/disclosure applies to Party Party communications coordinated with the campaign and to paid KYN polling?

How would the analysis change if FLA becomes an LLC/corporation or engages subcontractors?

Are there additional restrictions or reporting requirements for Committee-funded participant/pilot support, translation, travel, or in-person identity verification?

18. Implementation and publication checklist

18.1 Before open-source publication of this policy

Confirm title, policy ID, version, SPDX identifier, copyright/attribution, and canonical repository.

Add LICENSE, NOTICE, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT, changelog, adoption record, profile, and controls files.

Remove secrets, personal data, signatures, tax/bank information, private legal communications, restricted KYN/ballot records, and sensitive topology.

Validate all public links and source dates.

Map every normative MUST control to a machine-readable control ID.

Candidate/treasurer approve the exact public release; record digest and effective date.

18.2 Before publishing the $150,000 fundraising goal

Treasurer approves allocation, no-upward-revision rule, public milestones, and related-party disclosures.

Obtain written Wisconsin Ethics Commission advice or qualified campaign-finance counsel review.

Confirm contribution limits, prohibited-source controls, processor settings, reporting status, and recordkeeping. [S10][S17][S32][S33]

Publish Funding Plan, program relationship disclosure, privacy/security limitations, and no-pay-to-govern language.

Ensure contribution page pays the Campaign Committee, not FLA/Party Party.

18.3 Before the full-system SOW becomes financially effective

Freeze and sign Schedule A baseline/Background IP inventory.

Complete SOW schedules, milestone evidence, operations inventory, asset/provider ownership, and direct-cost rules.

Treasurer independently approves relationship, scope, values, obligations, and acceptance process.

FLA provides vendor/tax records; campaign establishes ledger/report workflow.

Identify technical, financial, privacy, security, accessibility, and legal reviewers.

Confirm no pre-effective work is being billed and any already-complete milestone value is replaced/reduced.

18.4 Before each implementation milestone payment

Confirm milestone remained within prospective scope and category capacity.

Review exact acceptance evidence, versions/digests, defects, exceptions, and residual risks.

Separate technical confirmation from financial approval.

Record acceptance/rejection/credit and update obligation.

Publish public-safe milestone/payment record after privacy/security review.

18.5 Before each managed operations payment

Confirm written activation and service inventory.

Review monthly operations report, outages, backups, deployments, incidents, direct costs, credits, and unresolved risks.

Confirm no full suspension/termination and no double payment for included stabilization.

Publish public-safe summary.

18.6 Before first KYN campaign poll

Adopt signed poll manifest identifying operator, sponsor, funding, class, eligibility, separate tallies, effect, privacy, challenge, and audit.

Separate KYN identity/evidence from authorization, ballots, and political answers.

Exclude donation, purchase, patron, Party Favors, and engagement status from vote weight/assurance.

Complete accessibility, abuse, recovery, insider, correlation, and deterministic tally tests.

No monetization or advertising upsell in voting flow.

Authorized humans approve opening/closing/publication; public verifier reproduces result. [S23]

18.7 Quarterly and release review

Reconcile official campaign ledger, program subledger, FLA books/invoices, provider records, asset inventory, SOW obligations, and public ledger.

Review unaccepted milestones, vendor debt, credits, reserve capacity, reallocation, and no-upward-revision compliance.

Review agent permissions, canonical policy version, source eligibility, foreign-national boundary, and access logs.

Audit shared costs and provider ownership back to actual evidence.

Review public disclosures, attribution/synthetic-media notices, KYN/poll manifests, licenses, SBOMs, and security advisories.

Review entity status, sponsors, subcontractors, clients, conflicts, and candidate/public-office transition risk.

Publish changelog and public-safe quarterly status.

19. Source notes and authority hierarchy

Primary reliance is placed on Wisconsin statutes, administrative rules, and Wisconsin Ethics Commission guidance. FEC materials are used only where federal law directly applies (foreign-national restrictions) or are explicitly labeled as nonbinding federal analogies. Tax notes are limited and require separate tax review. Source links were reviewed for this Version 2.0 draft on July 25, 2026. Public maintainers should revalidate current law and official guidance before each adopted release.

[S1] Wis. Stat. § 11.0101 - Definitions, including contributions, volunteer services, Internet activity, disbursements, and obligations. https://law.justia.com/codes/wisconsin/chapter-11/section-11-0101/

[S2] Wis. Stat. § 11.0202 - Candidate committee required; campaign financial activity generally must occur through the registered committee. https://law.justia.com/codes/wisconsin/chapter-11/section-11-0202/

[S3] Wis. Stat. § 11.0204 - Candidate committee reporting of contributions, disbursements, and obligations; itemization requirements. https://law.justia.com/codes/wisconsin/chapter-11/section-11-0204/

[S4] Wis. Stat. § 11.1104 - Unlimited candidate contributions from the candidate's personal funds or property. https://law.justia.com/codes/wisconsin/chapter-11/section-11-1104/

[S5] Wis. Stat. § 11.1105 - Fair-market valuation of contributed property and services. https://law.justia.com/codes/wisconsin/chapter-11/section-11-1105/

[S6] Wis. Stat. § 11.1113 - Sole-proprietorship contributions are treated as contributions by the proprietor. https://law.justia.com/codes/wisconsin/chapter-11/section-11-1113/

[S7] Wis. Admin. Code ETH 1.20 - Authorization, valuation, timing, and written records for in-kind contributions. https://www.law.cornell.edu/regulations/wisconsin/Wis-Admin-Code-SS-ETH-1-20

[S8] Wis. Stat. § 11.1208 - Prohibition on strictly personal campaign disbursements and obligations; foreign-national rule incorporated. https://law.justia.com/codes/wisconsin/chapter-11/section-11-1208/

[S9] Wisconsin Ethics Commission, Formal Opinion 2025 ETH 02 - Mixed personal/campaign computer and phone costs; campaign-only devices allowed, mixed flat costs rejected. https://ethics.wi.gov/Resources/20250805%20Open%20Session%20Materials.pdf

[S10] Wisconsin Ethics Commission - Prohibited Contributions, including corporate and foreign-national sources. https://ethics.wi.gov/Pages/CampaignFinance/ProhibitedContributions.aspx

[S11] Wisconsin Ethics Commission - Attribution/Disclaimer Requirements. https://ethics.wi.gov/Pages/CampaignFinance/AttributionRequirements.aspx

[S12] Wisconsin Ethics Commission - Requests for Advice; written requests and replies are confidential unless the requestor makes them public. https://ethics.wi.gov/Pages/Resources/RequestAdvice.aspx

[S13] Wis. Stat. § 11.1303 - Attribution and Wisconsin synthetic-media disclosures for certain AI-generated political communications. https://law.justia.com/codes/wisconsin/chapter-11/section-11-1303/

[S14] Federal Election Commission - Foreign nationals; federal prohibition applies to federal, state, and local election contributions and election-related decision-making. https://www.fec.gov/help-candidates-and-committees/foreign-nationals/

[S15] Federal Election Commission - Personal use and candidate-owned office rental. Included only as a federal analogy, not Wisconsin authority. https://www.fec.gov/help-candidates-and-committees/making-disbursements/personal-use/

[S16] Federal Election Commission - Use of corporate facilities and resources. Included only as a federal analogy for ordinary commercial terms. https://www.fec.gov/help-candidates-and-committees/making-disbursements/using-corporate-labor-facilities-resources/

[S17] Wisconsin Ethics Commission - Limited Activity Reporting Exemption; contributions, disbursements, debts, obligations, and candidate funds count toward the threshold. https://ethics.wi.gov/Pages/CampaignFinance/Exemption.aspx

[S18] Wisconsin Ethics Commission - Sunshine reports and transaction data are public after filing. https://ethics.wi.gov/Pages/CampaignFinance/ViewReports.aspx

[S19] Wisconsin Ethics Commission - Standards of Conduct for state and local officials. https://ethics.wi.gov/Pages/Ethics/StandardsOfConduct.aspx

[S20] Wisconsin Ethics Commission - Statements of Economic Interests disclose employers, investments, real estate, commercial clients, associated organizations, and creditors. https://ethics.wi.gov/Pages/Ethics/StatementsOfEconomicInterests.aspx

[S21] Internal Revenue Service - Crowdfunding receipts may be taxable depending on facts; maintain complete records. https://www.irs.gov/newsroom/irs-reminds-taxpayers-of-important-tax-guidelines-involving-contributions-and-distributions-from-online-crowdfunding

[S22] Wisconsin Department of Revenue - Occasional-sale exemption and seller's-permit threshold for taxable products and services. https://www.revenue.wi.gov/Pages/FAQS/Occasional-Sale-Exemption-QA.aspx

[S23] AI for Wisconsin Know Your Neighbor investigation and implementation-planning report, July 25, 2026. KYN_Pro_Investigation_2026-07-25.md

[S24] Internal Revenue Service - 2026 information-return rules; the general Form 1099-NEC threshold for reportable nonemployee service payments made in 2026 is $2,000. https://www.irs.gov/businesses/small-businesses-self-employed/am-i-required-to-file-a-form-1099-or-other-information-return

[S25] Wisconsin Sunshine official registrant page for Korey Streich Campaign Committee, registrant locator 1148727. https://campaignfinance.wi.gov/browse-data/registrant/1148727

[S26] AI for Wisconsin campaign site and FAQ identify the registered committee as Korey Streich Campaign Committee. https://www.ai-for-wi.com/ https://www.ai-for-wi.com/faq

[S27] U.S. Bureau of Labor Statistics - occupational wage information used only as general pricing context, not a legal fair-market valuation. https://www.bls.gov/ooh/computer-and-information-technology/software-developers.htm

[S28] AI for Wisconsin technical baseline - USPartyParty/ai-for-wisconsin-agent: public architecture, implementation status, implementation plan, acceptance criteria, and office transition materials. The repository defines Hermes as the runtime, Campaign Core as deterministic authority, public/restricted repository boundaries, and a system not yet fully accepted for production.

[S29] AI for Wisconsin Full Technology Program Funding Plan - $150,000 maximum campaign goal, July 25, 2026. AI4WI_Full_Technology_Program_Funding_Plan_150K_2026-07-25.md

[S30] Statement of Work No. 001 - Revision B: Complete AI for Wisconsin Open Civic Operating System, KYN, public website, verifiable polling, infrastructure, open-source release, and managed operations, July 25, 2026. AI4WI_FLA_SOW_001_REV_B_Full_Civic_Operating_System_2026-07-25.md

[S31] Creative Commons Attribution 4.0 International license. It permits sharing and adaptation for any purpose, including commercially, subject to attribution and indication of changes. https://creativecommons.org/licenses/by/4.0/

[S32] Wisconsin Ethics Commission - Contribution Limits. Current official page lists a $20,000 cumulative individual limit for Governor candidate committees. https://ethics.wi.gov/Pages/CampaignFinance/ContributionLimits.aspx

[S33] Wisconsin Ethics Commission - Prohibited Contributions. Corporations, associations, labor unions, and American Indian tribes may not contribute to candidate committees; committees may accept contributions only from U.S. citizens and permanent residents under the foreign-national rule. https://ethics.wi.gov/Pages/CampaignFinance/ProhibitedContributions.aspx

Appendix A. One-page operating reference

Appendix B. Public program budget and milestone register

B.1 Allocation ceiling

B.2 Public cumulative milestones

B.3 Implementation payment ceiling

Appendix C. Transaction and program-ledger minimum schema

Appendix D. Open-source repository and release checklist

ai4wi-business-operations-policy/
├── README.md
├── LICENSE.txt
├── NOTICE.md
├── CONTRIBUTING.md
├── SECURITY.md
├── CODE_OF_CONDUCT.md
├── CHANGELOG.md
├── policy/
│ ├── AIWI-OPS-001.md
│ ├── implementation-profile.yaml
│ ├── controls.yaml
│ └── ADOPTION.md
└── examples/
├── milestone-acceptance-template.md
├── monthly-operations-template.md
├── public-ledger-template.csv
└── restricted-register-template.csv

Release gate:

no secrets/PII/restricted records;

license/notice complete;

profile and controls validate;

source links checked;

changelog/adoption/digest complete;

public/restricted classification reviewed;

agents updated to exact release;

public rendering matches source.

Appendix E. AI for Wisconsin implementation profile

Fork maintainers should replace this profile and reassess every jurisdiction-specific legal source.

Appendix F. Control registry summary

The companion controls.yaml is the machine-readable source for agents and automated checks. Minimum control families:

Every control has: ID, statement, severity, owner, evidence, execution rule, public/restricted classification, and source section.

| AIWI-OPS-001 v2.0.0 | Public draft | July 25, 2026 | | | :---- | :---- |