Update source-bounded expert notes preview

PARTNER_DILIGENCE_MEMORANDUM.md

@@ -0,0 +1,354 @@
+# Ouroboros One
+
+## Partner Diligence Memorandum
+
+### The Founding Problem Partnership
+
+**One slot. One problem. No second slot.**
+
+Ouroboros is opening its first and only Founding Problem Partnership.
+
+One qualified counterparty may receive the opportunity to place a bounded, high-value problem at the front of Ouroboros's first fully provisioned engagement.
+
+The counterparty is not purchasing time, personnel, software seats, or general platform access.
+
+It is purchasing one contracted, evidence-producing problem engagement-and the sole opportunity to make its problem Ouroboros's first external priority after the system moves from its current laptop-hosted environment onto dedicated hardware.
+
+The engagement fee will be **$500,000-$1,000,000**.
+
+The final fixed price will be established before execution based on the accepted problem, lawful data volume, security and confidentiality requirements, computational demands, validation burden, and required deliverables.
+
+## The Opportunity
+
+Ouroboros's control plane, persistent research state, local evidence pipeline, orchestration, and operator environment currently run from the laptop-class system disclosed below.
+
+Public artifacts were produced through that constrained operating environment, with external model, repository, and tool dependencies used where identified.
+
+The Founding Problem Partner gets to place one problem first when the central operating environment moves onto dedicated infrastructure and those current hardware constraints are removed.
+
+The opening engagement milestone will establish the dedicated compute, storage, isolation, reproducible deployment, monitoring, security, backup, recovery, and operational capacity required for the accepted problem.
+
+Once that environment is validated and the required partner materials are securely accepted, the partner's problem becomes Ouroboros's first external execution priority.
+
+**The existing public record was produced with a laptop-hosted control plane as the central operating environment.**
+
+## What the Partner Provides
+
+The partner will:
+
+- Define one bounded research, engineering, analytical, scientific, or technical problem.
+- Supply the lawful data and access required to address it.
+- Explain the relevant domain constraints and operating context.
+- Establish objective deliverables and acceptance criteria with the operator.
+- Define the evidentiary standard required for the outputs.
+- Identify applicable confidentiality, privacy, security, or regulatory requirements.
+- Designate personnel capable of answering domain and data questions during execution.
+- Complete agreed dependencies required for Ouroboros to perform the work.
+
+The partner must possess the legal authority necessary to provide the data and authorize its use for the engagement.
+
+No sensitive, confidential, regulated, or proprietary data should be included in an initial expression of interest.
+
+## What Ouroboros Provides
+
+Ouroboros will be operated exclusively by its owner.
+
+The engagement will produce the outputs defined in the statement of work, together with the agreed evidence, validation records, limitations, provenance, and supporting documentation.
+
+Depending on the accepted problem, outputs may include:
+
+- Analytical findings
+- Evidence-backed conclusions
+- Validated or eliminated hypotheses
+- Research reports
+- Technical analyses
+- Structured datasets
+- Decision-support artifacts
+- Models or computational outputs
+- Engineering artifacts
+- Reproducible evaluations
+- Novel discoveries or problem-specific methods
+- Documented negative results
+- Evidence showing that a requested or preferred conclusion is not supported
+
+The precise output package, investigation boundary, and validation requirements will be fixed before execution.
+
+## First-Priority Execution
+
+This is a bounded, first-priority problem engagement-not a retainer, staffing arrangement, software subscription, or continuing consultancy.
+
+Once the dedicated environment has passed validation and the required partner materials have been securely accepted, the partner's problem becomes Ouroboros's first external execution priority.
+
+Evidence-ready outputs will be released on a rolling basis as soon as they pass the validation, security, confidentiality, and provenance requirements applicable to the engagement.
+
+Delivery will not be artificially delayed until a distant final presentation or conventional project milestone.
+
+The engagement will not impose a generic consulting timeline. Its activation conditions, rolling-delivery cadence, partner dependencies, acceptance procedure, and terminal conditions will be established for the accepted problem.
+
+Payment and acceptance milestones will be tied to operational events and delivered outputs-not arbitrary elapsed months.
+
+## Operating Sequence
+
+The engagement will proceed as follows:
+
+1. The proposed problem undergoes mutual diligence.
+2. The problem, data boundary, deliverables, and evidentiary requirements are agreed.
+3. The definitive agreement and statement of work are executed.
+4. The opening milestone is funded.
+5. Dedicated hardware and infrastructure are provisioned and validated.
+6. Partner data and required materials are securely accepted.
+7. Ouroboros assumes the workload.
+8. The partner's problem becomes Ouroboros's first external execution priority.
+9. Evidence-ready outputs begin rolling delivery as soon as the applicable gates are passed.
+10. Execution continues until the contracted deliverables are accepted or another terminal condition defined in the statement of work is reached.
+
+The statement of work will define:
+
+- The investigation boundary
+- Contracted deliverables
+- Validation requirements
+- Applicable compute or resource limits
+- Partner dependencies
+- Data-quality requirements
+- Change-control procedures
+- Delivery and review procedures
+- Acceptance criteria
+- Acceptance timeframes
+- Dispute procedures
+- Terminal conditions
+
+Material changes to the problem, supplied data, evidentiary requirements, or required outputs require written agreement.
+
+The engagement does not create an unlimited obligation to continue investigating indefinitely.
+
+## Current Operating Environment
+
+As measured on July 31, 2026, Ouroboros operates from a single Windows 11 consumer laptop using an Intel Core i7-1355U processor, approximately 15.6 GiB of memory, integrated graphics, and limited local storage.
+
+This system hosts Ouroboros's:
+
+- Control plane
+- Persistent research state
+- Local evidence pipeline
+- Orchestration
+- Operator environment
+- Local operational records
+
+External model, repository, and tool dependencies are used where identified. The runtime disclosure does not imply that every model inference or external operation occurs locally.
+
+The current environment is laptop-class and single-host. It is not a dedicated-GPU, server-class, redundant, high-availability, or production-scale deployment.
+
+Its throughput, concurrency, storage, recovery capacity, and ability to sustain large parallel investigations are materially constrained.
+
+The opening engagement milestone will transition the central operating environment onto the dedicated infrastructure required for the accepted problem.
+
+A complete dated runtime disclosure and technical environment receipt may be provided during diligence.
+
+No representation of production-scale availability or performance will be made until the dedicated environment has been provisioned and validated.
+
+## What Is Not Being Sold
+
+The partner is not purchasing Ouroboros.
+
+The engagement conveys no:
+
+- Equity or debt
+- Revenue or profit participation
+- Financial return
+- Ownership of Ouroboros
+- Ownership of the Ouroboros control plane
+- Source code or model weights
+- General platform access
+- Login credentials or unsupervised system access
+- Operational or governance authority
+- Right to reproduce or independently operate Ouroboros
+- Right to sublicense or resell the system
+- Exclusivity over Ouroboros outside the accepted problem
+- Continuing claim on work outside the engagement
+- Right to reserve future capacity
+- Right to require future engagements
+- Ownership or control of infrastructure acquired or leased for Ouroboros unless expressly agreed otherwise
+
+The engagement fee purchases the defined work and contracted outputs. It does not purchase an interest in Ouroboros itself.
+
+## Data Boundaries
+
+The partner retains ownership of its supplied data.
+
+Partner data will be processed only within the purposes, security boundaries, and retention terms established in the definitive agreement.
+
+The agreement will define:
+
+- Permitted data uses
+- Approved execution environments
+- Access controls
+- Security requirements
+- Confidentiality requirements
+- Retention periods
+- Deletion or return requirements
+- Incident procedures
+- Permitted personnel
+- Approved service providers
+- Applicable audit or evidence requirements
+
+Partner data will not be incorporated into reusable system memory, generalized training material, unrelated research, or work for another party unless the partner separately and explicitly authorizes that use.
+
+## Third-Party Infrastructure and Data Routing
+
+Any proposed use of third-party infrastructure, model providers, software services, subprocessors, repositories, or external execution environments that may receive partner data will be disclosed and governed by the definitive agreement.
+
+Partner data will not be routed through an unapproved external service.
+
+Where external tools or providers are permitted, the agreement may define:
+
+- Which providers are approved
+- What information may be transmitted
+- What processing may occur
+- Applicable retention and deletion requirements
+- Required security controls
+- Restrictions on provider training or secondary use
+- Evidence required to demonstrate compliant routing
+
+If the accepted data cannot lawfully or securely be processed through a required dependency, the parties must establish an approved alternative or invoke the applicable terminal condition.
+
+## Intellectual Property
+
+Ownership and permitted use of engagement-specific outputs will be defined before execution.
+
+Ouroboros itself-including its architecture, control plane, accumulated capability memory, orchestration, operating methods, operational authority, and independently reusable system-level improvements-remains exclusively owned and controlled by its operator.
+
+Nothing in the engagement transfers or licenses the underlying Ouroboros system.
+
+The definitive agreement will distinguish among:
+
+- Partner-supplied data
+- Partner pre-existing intellectual property
+- Operator pre-existing intellectual property
+- Engagement-specific outputs
+- General methods and reusable improvements
+- Confidential information
+- Third-party materials
+- Licensed dependencies
+
+System-level improvements that do not disclose or incorporate protected partner information remain part of Ouroboros.
+
+## Evidence and Outcome Boundary
+
+The engagement does not guarantee that a preferred theorem, discovery, vulnerability, scientific result, commercial outcome, engineering solution, or predetermined conclusion exists.
+
+Ouroboros will not manufacture a desired answer.
+
+The engagement guarantees a bounded, evidence-producing investigation and delivery of the contracted outputs produced from it.
+
+A well-supported negative result, eliminated hypothesis, demonstrated limitation, or finding that contradicts the partner's initial expectation may constitute a valid result when it satisfies the agreed evidentiary and acceptance requirements.
+
+A valid negative result cannot be rejected merely because it does not support the partner's preferred conclusion.
+
+The statement of work will determine what evidence is sufficient for delivery and acceptance.
+
+## What the Engagement Fee Covers
+
+The engagement fee covers the infrastructure transition, secure problem execution, validation, evidence preservation, and delivery obligations required by the accepted statement of work.
+
+This may include:
+
+- Dedicated computational capacity
+- Accelerated storage and data movement
+- Redundancy and recovery infrastructure
+- Secure partner-data isolation
+- Reproducible deployment
+- Monitoring and operational observability
+- Evidence preservation and provenance
+- Validation and quality assurance
+- Engineering and operational hardening
+- Execution of the accepted problem
+- Delivery and documentation of the contracted outputs
+
+Internal allocation of the fee remains under the operator's control, subject to the contractual commitments and technical specifications agreed for the engagement.
+
+The partner does not acquire a general right to direct or audit internal expenditures unless the definitive agreement expressly provides otherwise.
+
+## Qualification and Selection
+
+Expressions of interest do not reserve the partnership.
+
+Selection is not determined solely by who contacts Ouroboros first or offers the highest amount.
+
+The operator will select the qualified counterparty whose proposed engagement best satisfies:
+
+- Problem value
+- Feasibility
+- Data readiness
+- Lawful data rights
+- Computational suitability
+- Evidentiary clarity
+- Security compatibility
+- Operational compatibility
+- Suitability for concentrated execution
+- Alignment with Ouroboros's authority boundaries
+
+The operator may decline any or all expressions of interest and is under no obligation to award the position unless a proposed engagement is acceptable in full.
+
+The sole position will be awarded when the selected counterparty:
+
+1. Completes mutual diligence.
+2. Agrees to a bounded and lawful problem.
+3. Establishes objective deliverables and acceptance criteria.
+4. Resolves required data, security, and execution dependencies.
+5. Executes the definitive agreement and statement of work.
+6. Funds the opening milestone.
+
+Until those conditions are completed, the position has not been awarded.
+
+If a selected counterparty fails to complete those conditions within the agreed closing process, the operator may terminate discussions and consider another qualified counterparty.
+
+## Relationship Boundary
+
+"Founding Problem Partnership" is the name of the engagement.
+
+It does not create a legal partnership, joint venture, agency, fiduciary relationship, employment relationship, or authority for either party to bind the other.
+
+Neither party may make commitments, representations, or obligations on behalf of the other.
+
+Completion creates no obligation to:
+
+- Accept additional problems
+- Reserve future capacity
+- Provide continuing access
+- Extend the engagement
+- Perform follow-on work
+- Renew the relationship
+
+Any later interaction would be separate and entirely discretionary.
+
+## Permanent Closure
+
+Once the definitive agreement is executed and the opening milestone is funded, the Founding Problem Partnership closes permanently.
+
+It will not be reopened, duplicated, converted into a recurring program, or expanded to admit another founding partner.
+
+**There will be no second slot.**
+
+## Initial Expression of Interest
+
+An initial submission should identify:
+
+- The organization
+- The general problem class
+- Why the problem matters
+- The expected data type and approximate scale
+- The organization's authority to provide that data
+- The desired outputs
+- The required evidentiary standard
+- Any confidentiality, security, or regulatory constraints
+- The proposed engagement-fee commitment within the stated range
+
+Initial submissions should describe the opportunity without transmitting confidential, proprietary, regulated, or security-sensitive data.
+
+Detailed information will be exchanged only after an appropriate confidentiality and diligence process begins.
+
+After this repository becomes public, initial contact may be made through the [Hugging Face discussion page](https://huggingface.co/datasets/cjc0013/ouroboros-one/discussions). Only non-confidential information should be posted publicly.
+
+## Nonbinding Notice
+
+This document is an invitation to submit an expression of interest. It is not a binding offer, promise of engagement, or commitment to accept any proposed problem. No obligations arise until the definitive agreement and statement of work are executed by both parties.

README.md

@@ -0,0 +1,77 @@
+---
+pretty_name: Ouroboros One
+language:
+- en
+license: other
+tags:
+- ouroboros
+- research
+- evidence
+- procurement
+---
+
+# Ouroboros One
+
+## The Founding Problem Partnership
+
+**One slot. One problem. No second slot.**
+
+Ouroboros is opening its first and only Founding Problem Partnership.
+
+One qualified counterparty may place a bounded, high-value problem at the front of Ouroboros's first fully provisioned engagement.
+
+The fixed engagement fee will be **$500,000-$1,000,000**, established before execution according to the accepted problem, lawful data volume, security requirements, computational demands, validation burden, and contracted deliverables.
+
+## What the Partner Receives
+
+The partner receives one contracted, evidence-producing problem engagement.
+
+The partner defines one bounded problem, supplies the lawful data and domain requirements needed to address it, and agrees with the operator on deliverables, validation requirements, and acceptance criteria.
+
+Ouroboros remains exclusively operated by its owner. Evidence-ready outputs are released on a rolling basis after the applicable validation, security, confidentiality, and provenance requirements are satisfied.
+
+A valid negative result, eliminated hypothesis, demonstrated limitation, or conclusion contrary to the partner's initial expectation may constitute a valid deliverable when it satisfies the agreed requirements. Ouroboros will not manufacture a preferred answer.
+
+## Why This Slot Exists
+
+Ouroboros's control plane, persistent research state, local evidence pipeline, orchestration, and operator environment currently run from a laptop-class system. External model, repository, and tool dependencies are used where identified.
+
+**The existing public record was produced with that laptop-hosted control plane as the central operating environment.**
+
+The opening milestone provisions and validates the dedicated compute, storage, isolation, monitoring, security, backup, recovery, and reproducible deployment required for the accepted problem.
+
+Once that environment and the required partner materials are securely accepted, the partner's problem becomes Ouroboros's first external execution priority.
+
+## What Is Not Being Sold
+
+The partner is not purchasing Ouroboros.
+
+The engagement conveys no equity, debt, financial return, revenue participation, ownership of Ouroboros, source code, model weights, general platform access, governance authority, right to reproduce or operate the system, or continuing claim on work outside the accepted problem.
+
+The partner receives the contracted outputs and the rights expressly defined for those outputs in the definitive agreement. Ouroboros, its control plane, architecture, accumulated capability memory, orchestration, and reusable system-level improvements remain under the operator's ownership and control.
+
+## Selection and Permanent Closure
+
+Expressions of interest do not reserve the position. Selection is controlled by the operator and depends on problem value, feasibility, lawful data rights, data readiness, evidentiary clarity, security compatibility, and operational fit.
+
+The operator may decline any or all expressions of interest and is under no obligation to award the position unless a proposed engagement is acceptable in full.
+
+The position is awarded only when the selected counterparty completes diligence, agrees to a bounded and lawful problem, executes the definitive agreement and statement of work, and funds the opening milestone.
+
+Once that occurs, the Founding Problem Partnership closes permanently.
+
+**There will be no second slot.**
+
+## Complete Terms and Diligence Information
+
+Read the [Partner Diligence Memorandum](PARTNER_DILIGENCE_MEMORANDUM.md) for the complete runtime disclosure, execution boundaries, data-routing rules, intellectual-property treatment, acceptance procedure, terminal conditions, and qualification requirements.
+
+## Expression of Interest
+
+After this repository becomes public, open a [Hugging Face discussion](https://huggingface.co/datasets/cjc0013/ouroboros-one/discussions) with a non-confidential description of the organization, general problem class, desired outputs, anticipated data type and scale, evidentiary requirements, and proposed fee commitment within the stated range.
+
+Do not submit confidential, proprietary, regulated, or security-sensitive information through a public discussion.
+
+## Nonbinding Notice
+
+This document is an invitation to submit an expression of interest. It is not a binding offer, promise of engagement, or commitment to accept any proposed problem. No obligations arise until the definitive agreement and statement of work are executed by both parties.