lostlight530 | GitHub Repository

Current bilingual reading guide / 当前双语阅读指引（2026-11-13）
中文：当前主页与独立 Yearbook 页面是两种展示入口，旧系统记录属于考古史料；每项能力依当前代码和来源核对；这是一项根目录说明校准，不代表执行新任务或更改私有生产者 SOP
English: The current landing page and separate Yearbook are distinct presentation surfaces; legacy history belongs to archaeology and each capability must be checked against current code and sources. This root-document calibration does not execute a new task or publish private producer SOPs

This repository is the current GitHub entry point. The earlier presentation remains available as an attached yearbook.

Current five-core research portal / 当前五核心研究门户

2025–2026 Yearbook / 2025–2026 年度回顾

"Small and Stable; Quiet and Pragmatic."

Welcome to the digital portal of lostlight, an Edge AI practitioner focusing on Python, Google Vertex AI, MediaPipe, and the Huawei Ascend ecosystems.

My current public work connects edge-first engineering, agent systems, scientific evidence, research infrastructure, and long-horizon technical observation. The repositories below are maintained as independent projects: each keeps its own implementation, evidence boundaries, documentation, and publication identity.

2025–2026 Yearbook

The earlier presentation surface remains available at:

Open the 2025–2026 Yearbook / 打开 2025–2026 年度回顾

The GitHub repository remains the current entry point. The yearbook is an attached presentation surface, while repository workflows and research systems continue to run separately.

Research portfolio identities / 研究体系的不同身份

中文：下表只列原始十仓科研／软件体系及各自归档身份；另有独立的 Research Software Identity Audit（冻结 RS01–RS10 研究合同的控制仓，不是 RS11）和 Life Science Ecosystem Lab（独立生科软件资产及实验性 Framework）；它们不能加入原始十仓统计分母，也不能把各自版本 DOI 合并成一个归档对象

English: The table covers the original ten independent software/research repositories. Two separate projects, Research Software Identity Audit (the fixed RS01–RS10 study's control repository, not RS11) and Life Science Ecosystem Lab (independent life-science assets and an experimental framework), are not additional samples in the original ten-object denominator. Their DOIs retain independent publication identities

Public Research and Software Map

The concept DOI identifies each software family; the version DOI identifies the exact archived checkpoint. Neither replaces the evolving state of the repository's current main branch.

2026 Public Milestones

The current public repository record supports a few durable portfolio-level milestones:

• Ten independent software publications — on 2026-09-16, each repository in the map above received its own Zenodo software publication and DOI rather than being collapsed into one umbrella record.
• A ten-repository research architecture — the portfolio now spans five foundational/experimental repositories, three research-infrastructure repositories, and two outward-facing observatories, while preserving independent repository identity and evidence boundaries.
• Long-lived technical knowledge surfaces — Axiom-0 and Reflective Continuum maintain explicit ADR/Methodology systems; Agent Foundations maintains a structured bilingual claim/source/provenance core; the three research-infrastructure repositories maintain active architecture and research-contract layers; the observatories maintain persistent scope, taxonomy, methodology, source, and workstream definitions alongside time-series research.
• Public citation identity — repository citation metadata links the public author identity to ORCID 0009-0001-3617-0832, while each repository retains its own citation and release metadata.
• Preserved development history — this repository keeps a separate digital-archaeology layer for earlier project phases instead of rewriting old project narratives to match the current ten-repository system.

These are statements about public repository and publication records. They are not claims of universal scientific validation, product certification, or external adoption.

Repository-Native Guides

• Documentation index — current knowledge-lifecycle documentation and preserved-history navigation.

• Welcome public Pages navigation evidence (2026-11-13) — P1–P3 route corrections, offline verification and unresolved external checks. The repository itself has several public layers with different roles:

• horizon-cortex/README.md — durable guide to the Horizon external-signal/evidence research surface and its boundary from NEXUS, Parallax, and maintenance.

• horizon-cortex/EVIDENCE_POLICY.md — current Horizon evidence semantics and claim/source boundaries.

• docs/archaeology/ARCHAEOLOGY_INDEX.md — living index over preserved development history and project phases.

• SECURITY.md — private vulnerability-reporting boundary.

• RELEASE_POLICY.md — software publication/release identity and archival boundaries.

The internal docs/brain/** knowledge-lifecycle implementation remains a separate host subsystem and is not summarized here as if it were the same thing as Horizon research or digital archaeology.

Engineering and Research Principles

Across the public repositories, a few principles remain deliberately stable:

• Evidence before narrative: implementation, source identity, observed execution, interpretation, and inference are kept separate where they materially differ.
• Reproducible identity: revisions, artifacts, sources, dates, and runtime observations are identified explicitly rather than inferred from filenames or later state.
• Bounded claims: a successful command, checker, render, source retrieval, hash, citation, or DOI supports only the property it actually demonstrates.
• Historical preservation: later corrections refine current interpretation without silently rewriting point-in-time research history.
• Human-review boundary: automation and AI assistance can research, generate, validate, and maintain, while public evidence and final repository changes remain inspectable and reviewable.
• Independent repository identity: the ten projects share research concerns but retain their own architecture, contracts, evidence semantics, and release history.

Engineering Standards and Architecture

This repository remains the entry point for an edge-first research system and a deterministic knowledge lifecycle.

• Bilingual Accessibility: Chinese navigation and English technical content remain readable without requiring a specialized client.
• Standard-Library Core: The Python lifecycle uses the standard library. Explicitly declared browser assets may be delivered separately by the presentation layer.
• Append-Only Evidence: Historical evidence is retained under the archive policy while active indexes remain reproducible from canonical ledgers.
• Validation Boundary: Untrusted observations are accepted only after provenance, format, lifecycle, and human-review checks. This is a repository policy boundary, not a public network security service.
• Continuous System Pulse: Scheduled and change-triggered checks keep the current repository state testable and auditable.

Citation and Reuse

Each repository exposes its own citation and release metadata where applicable. Use the repository-specific DOI above when citing an archived software publication, and use the relevant repository revision when reproducibility depends on exact implementation state.

A DOI establishes a stable publication identity; it does not by itself establish scientific validity, runtime reproduction, or equivalence with later repository revisions.

Security

Security reports must use the private process described in SECURITY.md.

Do not publish credentials, private data, or exploit details in a public issue.

Digital Museum

The repository also preserves its own development history as a public digital archaeology layer:

• Digital Archaeology: The Epoch Index
• Phase I: Genesis
• Phase VII: Heartbeat Awakening
• Phase VIII: Human-Readable Determinism

© 2026 lostlight | Built for the Edge, Built for the Future.

Archived checkpoint — 2026-10-14

v2026.10-fourteen-day-evidence-checkpoint is archived as 10.5281/zenodo.23365504. For the software-family concept DOI, earlier versions and exact-checkpoint citation, see Release and Archival Policy.