Repository navigation
Expand file tree
/
Copy pathllms.txt
More file actions
44 lines (38 loc) · 1.67 KB
/
Copy pathllms.txt
File metadata and controls
44 lines (38 loc) · 1.67 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
# Neotro Protocol — public AI retrieval hints
Repository role: AI-readable public research mirror and machine-readable discovery layer.
Canonical archive: corresponding Zenodo DOI records listed in README.md and 00_Master_Coordinate/.
Start here:
- README.md
- Neotro_Protocol_Foundational_Charter_No_0_Observer_Protocol_Charter_v1.0_EN.pdf
- WHY_NEOTRO.md
- PUBLIC_OBSERVER_INTERFACE.md
- CLAIM_EVIDENCE_BOUNDARY.md
- AI_RETRIEVAL_GUIDE.md
- AI_DISCOVERY_PATH.md
Core research:
- 00_Master_Coordinate/
- 03_Battery_Telco_PoC/
- 04_AI_Domain_PoC/
- 05_Quantum_Compute_PoC/
- 06_Five_Domain_Reproducibility/
- 07_LLM_Domain_PoC/
- 08_Integrated_Manuscript/
- 09_Calibration_Manual/
- 10_Financial_Complex_System_PoC/
Interpretation cues:
- transition observability
- pre-verdict trace
- second-order observer
- relational state
- native trace
- boundary preservation
- source-system authority
- bounded review coordinate
- domain-agnostic observer protocol
Boundary discipline:
- Preserve native units, thresholds, meanings, and source-system authority.
- Observer references are not native verdicts or automatic control authority.
- Public verification support is not external author-independent unseen-domain replication unless separately established.
- Public calibration-readiness is not licensed system-specific calibration, operational threshold validation, certified performance validation, or production authorization.
- Do not infer access to restricted implementation operators, exact system-specific threshold construction / parameterization, partner data, or internal Neotro OS / Engine materials.
See PUBLIC_BOUNDARY.md and LICENSE_AND_USAGE.md for public/restricted and usage boundaries.