OSI / PIA Documentation Index

OSI / PIA Documentation Index

Purpose

This index is the front door to the OSI/PIA documentation system. It helps contributors locate foundational concepts, architectural decisions, research work, implementation guidance, and canonical project references.

Start Here

Public Publications

• Publications
• Articles
• Briefs and Project Updates
• Hiring Does Not Have a Talent Problem. It Has a Translation Problem.
• The False Negative Machine
• Real Capability vs. Manufactured Polish
• Hidden Workers and Capability Leakage
• The Wrong Metrics Are Steering the System
• The Future Is Not the Perfect Resume
• Poking a Hole in the Fog of ATS War
• What PIA/PCA Is Trying to Build
• What OSI Is Trying to Measure
• The False Negative Stack
• Access Is Not Authority
• When the Gate Is Right and Still Wrong
• Temporal Authority
• Capability Infrastructure Should Belong to the People It Describes
• You Can’t Find Work, and Companies Can’t Find Workers, Because the Labor Market Can’t Read People
• Project Bibliography
• PIA Professional Identity and Resume Output Model

Active Research and History

• Literature-Positioning Matrix
• PIA <-> Open Skills / LER Crosswalk
• Principle-to-Enforcement Crosswalk
• PIA and OSI Literature Positioning Notes
• Project Bibliography and PIA/OSI Literature Positioning Milestone

##

1. Guided Start Here
2. Project Status
3. Platform Overview
4. Repository Architecture
5. Repository Conventions
6. Namespace Standard
7. Clean Release Standard
8. Repository Registries
9. Governance Model (proposed at Congruence)
10. Governance Model Ratification Review
11. Foundational Principles
12. Human-Centered Capability Infrastructure
13. Glossary
14. Canonical Terminology
15. Project Vocabulary
16. Knowledge Lifecycle
17. Knowledge Management Governance
18. Congruence Protocol
19. Assurance Architecture
20. Concept Map
21. Ontology Meta-Model
22. Graph Architecture
23. Graph Ontology Crosswalk
24. Graph Standards

Documentation Domains

Architecture

Stable system design, structural relationships, component boundaries, and cross-cutting operating mechanisms.

Research

Exploration, hypotheses, evidence gathering, working models, and material not yet promoted into stable architecture.

Principles

Foundational commitments that guide architecture, implementation, governance, and interpretation.

Governance

Policies and protocols governing ecosystem use, decisions, responsibilities, and system behavior.

• Repository Architecture
• Repository Conventions
• Namespace Standard
• Clean Release Standard
• Repository Migration Plan
• Repository Registries
• Governance Model is the proposed constitutional consolidation of these authorities.
• Governance Model Ratification Review records Congruence findings, dispositions, and Validation evidence.

Knowledge Management Architecture

Cross-cutting structures governing how knowledge matures and is maintained:

• Knowledge Lifecycle
• Congruence Protocol
• Knowledge Management Governance
• Assurance
• Stewardship

ADRs

Architectural Decision Records preserve the context, reasoning, consequences, and status of significant design decisions.

• ADR Index
• ADR Registry

Components

Implementation-specific contracts, interfaces, behaviors, and technical guidance.

Ontology and Graph

• Core Concepts defines current technology-independent concepts.
• Ontology Meta-Model defines how ontology items, statuses, and projections are distinguished.
• Ontology Registry records stable shared, OSI, PIA, and implementation ontology identities and status.
• Graph Architecture defines shared graph layers and the separate OSI and PIA database roles.
• OSI Reference Database defines the organizational-system projection and acceptance boundary.
• PIA Reference Database defines the participant evidence projection and acceptance boundary.
• Graph Ontology Crosswalk records current, experimental, operational, and planned graph mappings.
• Graph Schema identifies which schema files are executable and which are descriptive.

Documentation Boundary

• Research is for exploration.
• Architecture is for stable design.
• Components describe implementation.
• ADRs preserve decision rationale.
• History preserves architectural evolution.

Knowledge should move from research into architecture only after sufficient formulation, congruence review, validation, and justified promotion.

Maintenance

Update this index whenever a new canonical project document is added, moved, superseded, or retired.