Mindling
Supporter Packet

Subject: I wanted you to see this first

Dear Aunt Christy,

I wanted to send this to you before I share it more widely.

The attached file is the current supporter package for Mindling, the product I have been building. Mindling is a local-first system for managing AI-assisted software work with structure, memory, evidence, review, and human approval. In plain English, it helps people use AI to build things without losing control of what was asked, what changed, what was proven, and what is actually safe to call done.

I am not sending this assuming anything from you. I am sending it because you are one of the people I trust most, and because I believe you may be one of the main people who can help me get this in front of the right family, friends, supporters, and community.

I am planning to launch a public support page soon. Before that happens, I wanted you and the family to have the first look. My hope is that this spreads through people who know me, believe in me, and understand that this is not just a product idea. It is also me trying to build a real future from the work I have been doing every day.

Right now, I am not offering equity, repayment, or a guaranteed financial return. This is not a securities offering. What I am asking for is early support to help fund the next stage of development: getting Mindling from a working internal proof into something other builders can use, test, and understand.

What early supporters would get is an inside view: private updates, early access when it is ready, and the ability to see the product take shape from the beginning. If Mindling later has a paid beta, customer launch, advisor path, or formal funding path, I would want the people who supported it early to be the first people I update, within whatever boundaries are appropriate at that time.

I believe the timing is real. AI tools are helping people build faster than ever, but the trust layer around that work is missing. People still need scope, memory, evidence, QA, review, and accountability. Mindling is my attempt to build that missing layer.

If you feel comfortable, I would be grateful if you read through the attached package and helped me think about who else should see it. Family, friends, people who support builders, people who care about technology, people who might want to sponsor the early development, or people who simply believe this should exist.

No pressure, and no assumption. I just wanted you to have it first.

Love,
Duane

What Mindling Is

Mindling is a local-first operating layer for AI-assisted software work. It helps a builder turn AI speed into scoped, reviewed, evidenced, and approved work instead of scattered chats, half-finished tasks, and uncertain closeout.

Mindling does not replace coding agents. It governs the work around them:

• what is being built;
• what context the agent receives;
• what evidence must come back;
• which review gate applies;
• what gets documented;
• when the human owner can safely approve the result.

Why Now

AI coding tools are already changing how software gets built. The next problem is not whether AI can produce code. The problem is whether a builder can trust, review, document, and close the work without losing context or control.

What Exists Now

• local app surface;
• issue intake and lifecycle behavior;
• local-first project state with optional external sync;
• agent and department routing model;
• QA and review gates;
• evidence-oriented workflow;
• exportable supporter package;
• 108 automated verification checks;
• internal company model with 15 department manifests and 14 explicit governed agent profiles.

The deck uses 125 as an estimated build-ticket-equivalent count, not as a literal historical issue count. It is a backcast from the product surface, tests, company model, deck, evidence, and workflow polish needed to reach the current proof.

The Ask

The immediate ask is development sponsorship, not a securities offering. Recommended initial support window: 90 days.

• Essential: $100/month
• Builder: $250/month
• Strategic: $500/month

What Supporters Get

Private progress updates, early access when usable, demo walkthroughs, visibility into what funding unlocked, roadmap influence, and first updates about future beta, paid product, advisor, or formal funding paths if those become appropriate.

Supporters do not receive equity, repayment, profit participation, revenue share, or guaranteed financial return through this sponsorship packet.

Development sponsorship means someone supports the build because they want Mindling to exist, want an inside view, or want early access to the product as it becomes usable. It does not create ownership, repayment rights, investment rights, profit participation, or revenue share.

Sponsor Levels

What Sponsors Receive

• Inside view of the build.
• Monthly progress report.
• Demo walkthrough at meaningful milestones.
• Early access when usable.
• Ability to submit workflow pain for consideration.
• Optional acknowledgement as an early development supporter.
• Early updates about future beta, paid product, advisor, or formal funding paths if those become appropriate.

What Sponsors Do Not Receive

• No equity.
• No repayment promise.
• No guaranteed return.
• No revenue share.
• No profit participation.
• No securities rights.
• No promise of future investment rights.

What is Mindling?

Mindling is a local-first operating layer for AI-assisted software work. It helps builders keep scope, context, evidence, review, and approval attached to the work that AI agents help produce.

What exists today?

Mindling has a working internal foundation: local app surface, issue intake, workflow guidance, routing, QA and review gates, evidence-oriented closeout, and a supporter deck that explains the current proof.

What is the immediate ask?

The immediate ask is a 90-day development sponsorship. The goal is to keep building, polish the demo path, prepare early-user onboarding, and turn the current internal proof into something easier for other builders to understand and try.

Is this an investment?

No. The current ask is sponsorship, not equity or repayment. Supporters are helping fund development and receiving an inside view, early updates, and early access as the product becomes usable.

What is still unproven?

External users, willingness to pay, final pricing, support burden, and the best first customer channel are still unproven. The 90-day sprint is designed to turn those unknowns into evidence.

Current Product Evidence

• Working internal product foundation.
• Local-first app direction.
• Issue intake and lifecycle behavior.
• AI-assisted workflow governance: scope, routing, evidence, QA, review, and owner approval.
• Internal company model with 15 department manifests.
• 14 explicit governed agent profiles.
• 108 automated verification checks.
• Supporter deck and packet ready for early conversations.

What The 90-Day Sprint Should Prove

• Whether the product can be explained clearly to people outside the build.
• Whether early users recognize the workflow pain.
• Whether a simple demo makes the value obvious.
• Whether someone besides the founder wants to use or sponsor the workflow.
• Whether the next step should be paid beta, continued sponsorship, advisor support, or a formal funding conversation.

This packet asks for development sponsorship and early support.

Supporters May Receive

• private progress updates;
• early access when the product is usable;
• demo walkthroughs;
• visibility into what sponsorship helped build;
• the chance to share workflow pain that may influence the roadmap;
• optional acknowledgement as an early supporter.

Supporters Do Not Receive

• equity;
• repayment rights;
• guaranteed financial return;
• revenue share;
• profit participation;
• investment rights;
• guaranteed future investment rights.

If a formal investment, advisor, revenue-share, or equity path ever becomes appropriate, it should be handled separately with proper legal structure. That is not what this sponsorship packet is offering.