Project History Brief: Independent Convergence with the Open Skills / LER Field

Origin

PIA did not begin as an attempt to participate in the Learning and Employment Records, open-skills, digital-credential, or skills-first ecosystems. Those fields were not part of the project’s original frame and were largely unknown during the initial design work.

The project began from a more immediate problem:

A person’s actual capability can be substantially greater than what conventional employment, education, credential, and resume systems are able to see or represent.

The initial PIA work therefore started from the individual rather than from an institutional data standard. The problem was not initially framed as one of interoperability. It was framed as one of recognition.

A person may have years of work, projects, informal learning, problem solving, artifacts, leadership, self-directed development, creative production, and cross-domain experience, yet the conventional record may reduce all of that to a small collection of job titles, degrees, certificates, and resume bullets. When those conventional signals poorly represent the underlying capability, both the individual and organizations lose access to useful information.

Building from the problem outward

PIA was developed by asking what would be required to reconstruct a more faithful account of capability from evidence of a person’s actual life and work.

That led independently toward an architecture involving:

collection of heterogeneous evidence from work, education, projects, credentials, artifacts, and lived experience;
preservation of source, context, provenance, and confidence;
relationships among people, activities, artifacts, outcomes, skills, and capabilities;
graph-based representation rather than a flat resume;
distinction between raw observations and higher-order capability inferences;
participant-facing outputs that explain what the evidence supports;
portable records intended to remain useful outside the PIA system; and
an eventual translation or socket layer capable of communicating those conclusions to existing employment and talent systems.

OSI developed alongside PIA from the opposite side of the same problem. PIA asks what capability exists and how it can be made visible. OSI asks whether an organization can recognize, trust, deploy, and develop that capability once it becomes visible.

The combined problem gradually became:

Capability can exist without being recognized, and recognized capability can still fail to become useful contribution if the surrounding system cannot absorb it.

Discovery of an existing field

Only after substantial portions of this architecture had already been conceived and implemented did the project discover the developed ecosystem around Open Skills, Learning and Employment Records, Rich Skill Descriptors, CTDL/CTDL-ASN, Comprehensive Learner Records, Open Badges, Verifiable Credentials, and related skills-first infrastructure.

That discovery was important for two reasons.

First, it demonstrated that many interoperability and representation problems PIA had encountered independently were already being addressed by serious standards efforts. PIA therefore does not need to invent proprietary replacements for portable credentials, competency definitions, verifiable records, or machine-readable employment data.

Second, the convergence helped clarify where PIA may actually belong.

Existing infrastructure is increasingly capable of answering questions such as:

What credential did this person earn?
What skill does it represent?
How can that information be transported between systems?
How can an employer verify it?

PIA began with an earlier question:

What does the total body of evidence indicate that this person can actually do, including capability that no previous institution has formally named, credentialed, or rewarded?

That distinction now appears fundamental to the project’s identity.

The individual must remain the primary beneficiary

The discovery of the established ecosystem also revealed a problem that reinforces PIA’s original purpose.

Much of the infrastructure intended to improve recognition of human capability exists several layers away from the individuals it is meant to benefit. It is frequently encountered through standards organizations, credential providers, workforce systems, educational institutions, HR platforms, employer systems, technical specifications, and policy initiatives.

For many individuals, the practical experience remains unchanged. They still face the question:

“I know there is more here than my resume shows. How do I figure out what it is, demonstrate it, and get someone to recognize it?”

The existence of sophisticated infrastructure does not automatically solve that problem if the individual cannot access, understand, populate, or benefit from it.

This is not merely a distribution problem separate from PIA’s subject matter. It is an example of the same underlying phenomenon PIA and OSI are trying to understand.

Useful capability can become sequestered behind systems that possess information about it but fail to convert that information into usable opportunity for the person who possesses the capability.

The same can happen to capability infrastructure itself.

Standards, taxonomies, credential records, and interoperable systems may become increasingly sophisticated while remaining largely invisible to people whose capability is underrecognized. The technical representation succeeds while the human conversion process remains incomplete.

A resulting design principle

This history suggests an important design constraint for PIA:

The individual should not have to become an expert in the capability infrastructure in order to benefit from it.

A participant-facing PIA system should be able to begin with ordinary human material:

Tell us what you have done.
Show us what you built, learned, solved, changed, taught, or discovered.
Preserve the evidence.
Determine what it reasonably supports.
Show the person what the system sees and why.

The complexity can remain underneath.

Graphs, ontologies, competency standards, skill alignments, CLR structures, verifiable credentials, and HR interoperability should serve the individual rather than become prerequisites the individual must master.

This leads to the working architectural principle:

PIA should be maximally expressive internally, maximally interoperable externally, and maximally understandable to the person whose capability it represents.

Why the independent development matters

The significance of independently converging on parts of the Open Skills/LER architecture is not that PIA invented concepts that others had already developed.

The more useful historical fact is that the project reached many of the same structural requirements by beginning from a different end of the problem.

The established ecosystem largely asks how learning, skills, credentials, and employment records can become portable, interoperable, verifiable, and useful across institutions.

PIA began by asking:

Why is this person’s actual capability still difficult to see?

Those paths converge technically, but their starting assumptions differ.

That difference may help identify PIA’s contribution:

Use the lived evidence of the individual to discover and explain capability first; then use established infrastructure to carry that evidence wherever it needs to go.

Project direction

The discovery of the Open Skills/LER ecosystem therefore does not make the PIA work redundant. It provides an established infrastructure beneath it and a clearer boundary around the research problem.

The emerging division of labor is:

PIA discovers, organizes, interprets, and explains capability.
The translation layer maps those conclusions into established skills and LER representations.
Existing standards provide portability, verification, and interoperability.
OSI investigates whether organizations can convert those signals into trust, opportunity, deployment, development, and mobility.

The long-term objective remains deliberately human-facing:

The purpose of capability infrastructure is not merely to produce better records about people. It is to increase the probability that real people gain access to work, learning, relationships, tools, and opportunities commensurate with what they can become and contribute.

The project began because that conversion had failed for an individual.

The discovery that a substantial technical field already exists—but remains largely invisible to many of the people it is intended to serve—does not weaken that original premise.

It makes the problem clearer.

Boundary

This is a public supporting project-history brief. It records the development logic behind the current PIA/OSI crosswalk and human-centered principle. It is not a systematic literature review, a novelty claim, a credentialing decision, or an authorization for production participant processing.