added

tasks-workflows/min-viable-product-build.md

@@ -0,0 +1,36 @@
+# What specifically must be true when this is done? Define in terms of metrics (revenue, costs, use metrics, etc), user flows, user delight, the feeling achieved when this outcome is realized, what it allows, where it can lead, how it leverages.  
+
+1. Homepage for nSIG.earth that resolves to nSIG.indx.earth.  
+- Describes the platform, why, how and what they get from it.  Keep it short, brief
+
+2. Signup page:
+- instreuctions to become a member, which is complete PID-template, save to google drive or onedrive, open persmissions for viewing, provide the URL and email and submit.  
+- T&C and disclaimer agreed to before submit
+- include your referral URL to signup.  
+
+3. ON sign-up
+- System takes the email and PID URL, creates a JSON file representing the user and their PID.  Stores this data in the JSON. Creates a referral URL as well unique to this person. 
+- System displays confirm page we got it.  Check your email. 
+- System sends them email confirming membership, the basic logic commands to interact with system, what to expect in terms of future emails and matching.  But we are alpha version, so be honest and tell people nbot matching for awhile.  We are building.  Forget about us, but white list the email from us.  Build your PID - improve it, think about it, etc.  Use this time to get it right for you.  Also include link inb email that confirms their email to our system.  Gives them a referral URL so they can tell others.  But, restircit it to 5 people each to start.
+- As admin, I can change that for each person.  My JSON may have more so I can send out to more people. 
+
+4. System Logic/Scripts
+- Referral URL restrictions - how many times can each one be reused?  To start, limit to 5. Coutner in the user JSON file that winds down when all 5 used.  
+- Optional to shut off all new submissions form system as a global rule, so we can stop getting new referrals.   
+
+What are the non-negotiables? (safety, cost, time, inputs)
+1. System adheres to system.md to be simple, fast, secure, basic, just works.  Nothing fancy or advanced.  
+
+Sequences, tasks, modules, dependencies, components
+ - na
+
+Vague input → mediocre AI output
+Precise constraints → high-quality execution
+ - what is vague about above that needs to be improved to provide clarity to AI to complete thie build-plan?
+
+Think in terms of outcomes - what you want to see when all is done.
+- A basic system as above that accepts submissions, nothing else.  No processing.  We want to start to build interest, get people to think about their PIDs. This 
+
+Break that outcome into components, dependencies, unknowns. You are converting the outcome, or problem, or rask or idea into machine-operable structure. 
+
+Turn messy reality of achieving outcomes into machine-readable objects, which are the documents and how they are structured throughout the Product Dev OS framework