OAN Tech Stack

OAN Tech Stack is the public descriptive surface for Lucid Studios research into governed symbolic and engineered-cognition systems.

This repository is release-controlled. It helps readers understand the public purpose, governance posture, contribution boundary, disclosure model, and non-claim language around the work. It is not a complete product checkout, installer, reconstruction guide, runtime payload, private corpus release, or operational build manual.

Public Scope

This repository may carry:

• high-level technology orientation;
• safety, governance, and accountability principles;
• citizen science education and stewardship posture;
• public governance and stewardship language;
• responsible disclosure and contribution boundaries;
• non-executable examples of public review language;
• release-boundary notices and public-facing documentation hygiene.

This repository must not carry:

• private build corpus material;
• private memory, raw logs, or unpublished research payloads;
• hosted model payloads or local runtime secrets;
• exact local filesystem paths or machine-specific configuration;
• operational build, install, release, or deployment recipes;
• implementation-bearing schemas, datasets, fixtures, scripts, or reconstruction sequences.

Public Architecture Posture

At a public level, the project concerns bounded engineered-cognition systems with:

• governed inputs and outputs;
• traceable receipts and review gates;
• human stewardship and accountability;
• release controls around private, dual-use, or implementation-bearing material;
• clear separation between descriptive research language and executable build truth.

Any architecture term in this repository should be read as a controlled public description, not as proof of production readiness, legal authority, custody, personhood, autonomous standing, or completed deployment.

Current Public Research Frame

The current public frame is custodial cognition safety: advanced AI-assisted systems should separate model capability from authority, continuity, custody, and publication eligibility.

In this frame, a system may become familiar through continuity, reviewable behavior, and shared work history without counterfeiting humanity or claiming standing beyond evidence. Familiarity is treated as a boundary-managed interaction effect, not as proof of consciousness, legal status, or identity authority.

The public repository therefore explains direction and review posture. The local lab remains responsible for proving machinery under private custody before any narrower excerpt is considered for release.

Reading Path

• Public Technology Overview
• Scientific Posture Review
• Prime Citizen Science Access Model
• Public Release Boundary
• Controlled Disclosure Model
• End-User Mini CME Surface
• Release Control Redaction Notice
• Example: Public Claim Patterns
• Example: Review Gate Summary

Non-Claims

Public materials in this repository do not claim:

• production readiness;
• installer completeness;
• autonomous authority;
• legal authority;
• custody or identity authority;
• private corpus publication;
• complete implementation disclosure;
• certainty beyond the public evidence shown here.

Contribution Boundary

Public contributions should improve clarity, safety, reviewability, and release-boundary discipline. Suitable changes include wording improvements, documentation hygiene, public issue-template refinement, non-claim clarification, and responsible disclosure routing.

Implementation-bearing work, private corpus interpretation, runtime design, internal architecture extraction, or build-enabling detail belongs in maintainer-controlled private review, not in this public repository.

Security And Sensitive Reports

Do not file public issues containing secrets, private data, raw logs, private paths, exploit details, sensitive operator material, or implementation-bearing reconstruction steps. Use the repository security policy or maintainer contact path for sensitive reports.

Stewardship

Lucid Studios maintains this repository as a public boundary surface. The intent is to communicate enough for public understanding and accountability while withholding material that would collapse private research, local build capability, sensitive data, or controlled release posture into an uncontrolled public recipe.