===== March 10, 2024 Annotated Agenda ===== * draft a multi-agent utility function for the WG * success criteria for the working group for multiple stakeholders required products for several people * Short term * generate resources on a timely basis * do not burn out * Populate RQ.com landing page - single page - by Friday Mar 22 * populate Requisite Q website front pages by the time the simulations are ready * develop corporate documents * develop [[Investor Documents]] * organize Paul's writings * [[blog posts]] generate website traffic measurable by SEO that shows growth * Long term * Show that our documents are useful to running the company and getting investors * Generate the option to come on board RQ full-time * it is also the generalized utility function (e.g., minima, maxima, target, confluence of interest, required products, etc.) * Products * Create Project documentation tree * Create Project Taxonomy * Create Project Glossary/Dictionary * establish housekeeping: * backlog * * Gary will standup a RequisiteQ wiki under the https://www.build-a-world.com * calendar * Geordie will standup a shared calendar * Working agreement * Geordie, Nathan, and Gary are pleased to work together to define and articulate project narratives. * catalog our understanding of the audiences and media for narratives * We need to add a catalog of resources accessible on the wiki * We have shared workspaces based on audiences * Internal project team (Confidential access) * Investors (Restricted access) *  Pitch Deck Evolution * • The top 10 +/- 2deck (top-down approach) “What Amit needs, . . .” * o Classic investor pitch deck * o How can we array the data for each slide in the deck * o What is the visualization *  Qbits, squids, in a helium bath *  Hardware  Problem Space  Solution Space * o Amit will join the Sunday narrative working group meeting * • The middle-out approach to drawing out the relationship between a top-down and bottom-up approach * o our context * o the problem space * o the potential solution space * o our product(s) *  Project Plans * • Technical considerations (1 page briefs, top priority) * o Outcomes (So what!?) * o Foundational technology * o Applications * o Development path * • Technical & Financial Considerations * • Financial considerations * o Budget template * o labor considerations * o contracting terms & conditions *  Market considerations (for-profit) *  Objective considerations (non-profit) *  Lessons learned  provisional patents * o Public (Open access) *  Recruitment *  Media resources * • Audio * • Video * • Web site * • Written content * o Op ed * o Magazine articles * o Abstracts for national and international fora * o Technical papers and presentations * • Funding Development * o Grants * o Contracts * o Financing *  Equity *  Debt *  Grants * o Audience drives the presentation *  Non-profit entity typically has defined goal or program objective to achieve and we must establish relevance *  For-profit entity typically wants to understand the ROI both a direct monetary return and the potential for disrupting and/or making new markets. * o Find the way to yes *  Only poke the bears we have to *  * - make a shortlist of necessary narrative materials * - review existing materials for suitability * * Things that we need to include . . . * • Investor brief, accessible * • Inspirational engagement brief, bigger than yourself * • Relevant technical concept and applicability in one or more contexts * * Priorities * • Technically correct -- Paul * • Emotional hooks – Amit * • So what!? – Investors * Concerns * • Conceptual markers * • Use cases * • We need stories that provide conceptual entry points * • Tell the story from the theory to the application and from the application to theory * *