GOBEKLI’S PROPOSED ARCHITECTURE
What Is a Human Intelligence Layer?
Connect what systems record with what people understand.
A Human Intelligence Layer is Gobekli’s proposed architecture for connecting human experience, evidence, and context into an evolving understanding that people, organizations, and AI can use.
It is designed to help people understand and communicate their capabilities, help organizations understand how work actually happens, and give AI relevant context within clear boundaries.
The purpose is to strengthen human agency and collective capability together.
We have records of activity. We still struggle to understand the experience behind it.
A résumé lists roles. A transcript lists courses. A project system records tasks. A dashboard reports outcomes.
Each captures something useful. The relationships between those records—and the human context behind them—can remain difficult to see.
What did someone actually contribute? Where did judgment matter? What conditions helped the team succeed? Which capabilities have grown beyond a person’s job description?
Those questions matter to the person seeking recognition and to the organization deciding what to do next.
People struggle to make their experience understood.
A person’s learning, responsibilities, accomplishments, and relationships accumulate across many settings. When an opportunity appears, they must compress that experience into another application, profile, or conversation.
Relevant capability can go unrecognized. Evidence becomes disconnected from its story. People may struggle to see how their own experiences connect—or where those experiences could take them.
Organizations struggle to understand how work happens.
Formal roles and system records provide an important view of an organization. They can leave out the informal coordination, practical knowledge, trust, and judgment that keep work moving.
Leaders may see a missed target without understanding the constraint behind it. They may hire for a capability someone already possesses, or introduce automation without seeing the additional work it creates.
A Human Intelligence Layer is intended to help people and organizations examine those gaps together.
Human intelligence is more than a list of skills.
In Gobekli’s framework, human intelligence means the connected understanding through which people and groups become capable of acting.
It includes experience, knowledge, judgment, motivation, relationships, trust, goals, and potential—as they appear through activities, evidence, decisions, and change over time.
A skill label can point toward a capability. Understanding that capability requires context.
“Leadership,” for example, could describe coordinating volunteers, supervising a shift, guiding a technical team, or making decisions during a crisis. The label becomes more useful when we understand what happened, under what conditions, and with what evidence.
The aim is to make more of that context available for a relevant purpose while keeping the limits of the representation visible.
Two connected pillars. Value on both sides.
A Human Intelligence Layer should help individuals and organizations develop their own understanding, with clear boundaries around what they exchange.
Gobekli’s proposed implementation has two connected pillars.
TalentPass: understanding that begins with the person
TalentPass is designed to help someone connect work, learning, experience, evidence, relationships, and goals into a living record.
From that foundation, a person can explore questions such as:
- What have I learned across these experiences?
- What evidence supports my capabilities?
- What patterns or possibilities have I overlooked?
- What would help me grow?
- What should I share for this particular opportunity?
The same experience can support different profiles without requiring someone to rebuild their history each time.
TalentSync: understanding that helps an organization act
TalentSync is designed to help organizations connect information about people, work, capabilities, relationships, and outcomes.
It supports questions such as:
- How does work differ from the official description?
- Where are capabilities being used—or overlooked?
- Which responsibilities lack sufficient support?
- Where does knowledge depend on too few people?
- How are changes affecting teams and workflows?
Organizational self-awareness means developing a more useful, revisable understanding of how the organization works.
Passport Pages connect the relationship.
Passport Pages are designed to support permission-based connections between people and organizations.
The exchange should have a clear purpose: what information is needed, who can use it, and what value the relationship returns.
Individual records and organizational records have different responsibilities. Connecting them should preserve those distinctions.
How experience becomes useful understanding
Consider an employee who helped resolve a recurring production problem.
The project system records that the issue was closed. It may say little about the troubleshooting, coordination, or knowledge that made the resolution possible.
A Human Intelligence Layer could support a more complete journey.
1. Explain the experience
The employee describes the problem, their contribution, the constraints, and what they learned.
Guided questions help clarify details without treating the first account as complete.
2. Connect the evidence
Relevant records, work samples, and other perspectives support or qualify the account.
The system keeps clear which information was self-described, externally attested, or inferred.
3. Create a view for a purpose
The employee uses selected experience and evidence in a development or team profile.
They share the context relevant to that conversation rather than exposing their entire record.
4. Use it in a decision
The manager and employee examine what the experience suggests about future responsibilities, development, or knowledge sharing.
The profile supports their judgment. It does not settle the decision for them.
5. Learn from what happens next
New responsibilities create new experience. Feedback may strengthen an earlier interpretation, reveal a gap, or suggest a different direction.
The understanding develops through use and revision.
This is an illustrative workflow for the proposed architecture. Available capabilities vary by product and stage of development.
Four features connect the experience
Each feature has a distinct role in Gobekli’s implementation.
Pythia: ask, reflect, and interpret
Pythia is designed to guide dialogue about experience, goals, work, and evidence.
Its role is to help people and organizations ask better questions, clarify meaning, and examine possibilities. Interpretations should remain open to correction.
Talent Tree: connect the underlying relationships
The Talent Tree is designed to connect activities, experiences, capabilities, evidence, and other context.
For organizations, those relationships can help distinguish capabilities in use, relevant experience that is not currently being applied, and areas where additional capability may be needed.
Profiles: make relevant understanding usable
Profiles organize selected information around a particular purpose.
An application, team conversation, learning plan, or workflow review may need a different view of the same underlying experience. A useful profile makes its evidence, scope, and uncertainties understandable.
Passport Pages: connect people, organizations, and systems
Passport Pages are designed to support the relationships through which relevant information can be requested, shared, and used.
They provide a place to make the purpose and boundaries of an exchange explicit.
The feedback loop depends on participation and returned value.
People contribute context when they understand the purpose and can see a reason to participate.
That contribution might support recognition, learning, a better work arrangement, a stronger application, or a useful conversation.
Organizations also need value: clearer evidence, better coordination, fewer unresolved assumptions, and a stronger basis for decisions.
The intended cycle is:
Contribute experience → connect evidence → develop understanding → act → learn → revise.
Participation creates opportunities for richer understanding. Whether the cycle continues depends on trust, usefulness, and what participants actually receive in return.
Trust must be designed into the architecture.
Making human context more visible creates power. The same information that supports development could also be used to categorize, monitor, or disadvantage someone.
Gobekli proposes six design responsibilities for a Human Intelligence Layer.
1. Meaningful participation
People need understandable ways to contribute experience, evidence, and feedback—and meaningful value from doing so.
Developmental reflection should have appropriate protection from unrelated evaluation.
2. Guided dialogue and reflection
People should be able to explain what a record leaves out, examine interpretations, and add context as their understanding changes.
Questions should help people articulate their experience without forcing every story into the same categories.
3. Evidence and provenance
A trustworthy representation distinguishes self-description, issued records, observations, and machine inference.
Readers should be able to understand where a claim came from and what supports it.
4. Connected context
Information should retain the relationships that make it meaningful: activities, purposes, circumstances, evidence, and change over time.
A connection should clarify an interpretation rather than create an appearance of certainty.
5. Purpose-bound access and use
Sharing should be proportionate to the task. People need clear information about access, permitted uses, retention, and their available choices.
Agreement to one exchange should not silently authorize unrelated evaluation.
6. Returned value, correction, and continuing governance
Participants need ways to benefit, identify errors, challenge consequential interpretations, and influence rules that affect them.
Portability and usable exit arrangements matter alongside ongoing participation.
These are proposed design responsibilities. The white paper develops their reasoning and examines the tensions between individual agency, organizational needs, and shared governance.
AI needs context—and a defined place in the decision.
AI may help summarize experience, connect related information, identify missing evidence, or prepare questions.
Those uses become more accountable when people can distinguish:
- What a source actually says.
- What a person has explained.
- What the model has inferred.
- What remains uncertain.
- Who is responsible for the resulting decision.
More context does not automatically produce a correct interpretation. Nor does the ability to infer something establish a right to use it.
A Human Intelligence Layer should make the basis and boundaries of AI assistance easier to examine.
Built on portable records. Extended through human context.
Learning and Employment Records and verifiable credentials provide important foundations for carrying achievements and attributable claims between systems.
A Human Intelligence Layer addresses an additional question: how can those records remain connected to the experience, interpretation, relationships, and purposes that make them useful?
The two ideas are complementary. Portable records help information travel. Human participation helps explain what that information means in a particular situation.
Start with a problem people recognize.
An organization does not need to map everything before making progress. Begin with a decision or recurring difficulty where missing context matters.
AI transformation
Understand how work is changing, where human judgment remains essential, and what support people need.
Workforce readiness and scalability
Examine responsibilities, capability needs, knowledge coverage, and the conditions required to take on more work.
Organizational growth
Clarify how roles, coordination, culture, and operating practices need to change as the organization develops.
Learning, membership, and public services
Explore how people’s experience and goals can inform programs, relationships, and continuity between organizations.
Explore more workshop starting points
Find a workshop for a specific learning, membership, workforce, or infrastructure challenge.
Explore applications of the architecture
Explore approaches to learning, service, leadership, and recruiting. See product availability for the current stage of development.
The deeper argument: Building the Best Possible Future
What kind of future are we building when intelligent systems increasingly interpret people and organize their opportunities?
Danny Done’s white paper examines the philosophical and practical foundations of Gobekli’s proposal: human agency, collective intelligence, self-authorship, evidence, institutional power, and shared governance.
It connects those questions to the architecture of TalentPass, TalentSync, and the Human Intelligence Layer—and examines the limits needed to keep that architecture accountable.
What is available today?
This page describes Gobekli’s proposed architecture and the direction of our product development.
TalentPass, TalentSync, and their features are at different stages of availability. Workshops and collaboration can help scope a practical starting point; they do not imply that every described software capability is ready for deployment.
Common questions
Is “Human Intelligence Layer” an established technical standard?
On this page, the term describes Gobekli’s proposed framework. Its implementation can draw on existing standards, but the framework itself should not be confused with an independently established specification.
Does it replace existing systems?
The proposed architecture connects relevant information across people and systems. The role of an existing HR, learning, project, or customer system depends on the implementation and the use case.
Does it require everyone to share everything?
No. The proposed approach depends on selecting relevant information for a defined purpose and establishing appropriate boundaries around access and use.
Is it only about skills?
No. Skills are one part of the picture. The framework also considers experience, judgment, relationships, knowledge, goals, responsibilities, and the conditions that affect how people work and learn.
Does it create one definitive profile of a person?
No. Profiles are purpose-bound perspectives. They should remain connected to evidence, open to correction, and limited in what they claim.
How does an organization begin?
Choose one problem where missing context affects a real decision. Identify the people involved, the evidence available, and what better understanding would allow them to do. Then scope an approach that can be tested and revised.
Build a clearer understanding of what comes next.
Start with the people, work, and decisions you need to understand better.
We can help you examine the gaps, identify a useful starting point, and explore how human intelligence could support your next step.