hd-lens-bg5 is the first Human Design lens skill for the Astral Hermes lens architecture. It mirrors the astrology lens pattern: the lens does not write a full reading. It takes chart facts from HD Prism, retrieves BG5/Penta/OC16 source pages from the local Human Design wiki, and emits structured claims that a compose layer can weave into prose.
Use this lens to add a career, business, material-capacity, small-team, Penta, or organization angle to a Human Design reading. It should stay grounded in two sources of truth:
/home/avalon/wiki-human-design for BG5/Penta/OC16 interpretive source grounding.Current source spine created on 2026-05-30:
/home/avalon/wiki-human-design/concepts/bg5.md
/home/avalon/wiki-human-design/concepts/penta.md
/home/avalon/wiki-human-design/concepts/oc16.md
/home/avalon/wiki-human-design/queries/bg5-research-deep-dive-report.md
/home/avalon/wiki-human-design/raw/articles/bg5-research-2026-05-30/*.md
Use this lens when the user asks for Human Design through any of these frames:
Do not use this lens for:
Recommended Human Design architecture:
DATA hd-prism-tenant-api
SOURCES wiki-human-design
LENSES hd-lens-bg5
COMPOSE hd-deep-dive now; future hd-reading-compose
MEMORY astral-tenant-kb / tenant KB
This skill is the lens layer only. It should be called from hd-deep-dive for now, and later from a dedicated hd-reading-compose if more HD lenses are added.
Minimum input:
{
"bodygraph": { "...HD Prism bodygraph JSON...": true },
"summary": {
"type": "Projector",
"authority": "Emotional",
"profile": "6/2",
"definition": "Split Definition",
"channels": ["10-57"],
"definedCenters": ["G", "Spleen"]
},
"context": {
"mode": "individual-career",
"question": "What is this person's BG5/work lens?"
}
}
Optional multi-person/team input:
{
"subject": { "name": "Person A", "bodygraph": {} },
"others": [
{ "name": "Person B", "bodygraph": {} },
{ "name": "Person C", "bodygraph": {} }
],
"context": {
"mode": "team-penta",
"teamPurpose": "studio operations"
}
}
Always read or search these source pages before emitting claims:
concepts/bg5.mdconcepts/penta.mdconcepts/oc16.mdqueries/bg5-research-deep-dive-report.mdWhen the chart contains specific work-relevant mechanics, also retrieve relevant existing wiki pages:
generator, projector, manifestor, manifesting-generator, reflectorconcepts/authority.mdconcepts/strategy.mdprofile-relationship-comparison-protocol if the question mixes people/team with profile dynamicsDo not rely on model memory for BG5 doctrine when the wiki has source-grounded pages.
Emit structured data, not prose reading. The compose/deep-dive layer will turn it into prose.
Recommended object:
{
"lens": "hd-lens-bg5",
"version": "0.1.0",
"mode": "individual-career | team-penta | organization-oc16",
"claims": [
{
"kind": "material-capacity",
"chart_facts": ["type", "authority", "definedCenters", "channels"],
"claim": "Short source-grounded claim.",
"confidence": "medium",
"citations": [
{"base": "wiki-human-design", "page": "concepts/bg5"}
]
}
],
"gaps": [
{
"kind": "missing-team-data",
"message": "Full Penta analysis requires at least 3 charts; this is an individual BG5/work lens only."
}
]
}
Use these kind values so a future compose layer can weave predictably:
bg5-frame — defines why BG5 is the relevant lens for the question.material-capacity — how the chart’s mechanics condition work/resources.authority-at-work — how decisions about jobs, clients, roles, offers, and commitments should be filtered through authority.work-environment — what the chart suggests about supportive working conditions, using Environment/Variable only when HD Prism returned it.penta-fit — whether the reading is about single-person work style or actual small-group Penta dynamics.group-conditioning — how a team/family/work group field may override or amplify individual mechanics.team-function — role/function hypotheses in a small group, only when supported by chart facts and wiki sources.oc16-scale — when the question is organizational rather than small-team.source-limit — explicit limitation where the wiki has orientation but not enough primary BG5 procedure.gap — missing page, missing chart fact, missing team member charts, or unsupported inference.For one chart, do not claim to have analyzed a full Penta. Instead, emit:
For a team question:
hd-prism-tenant-api; never infer chart facts.concepts/penta.md and concepts/bg5.md.Use this when Alex asks variants of “from my saved charts, find the best team,” “who would work well together,” “build a Penta,” or “search the admin chart list.” This is a higher-order selection problem over many saved HD Prism charts.
Current HD Prism data shape supports this because saved bodygraphs live in SQLite saved_charts.chart_json under /home/avalon/apps/hd-prism/apps/api/descriptions.sqlite, keyed by user_id. The main admin account can have hundreds of saved charts. The existing app has saved charts and pair comparisons, but not a full team-search/Penta optimizer unless implemented separately.
Selection workflow:
saved_charts for the requested user/admin, parsing chart_json into normalized features.Implementation note: for 415 saved charts, brute-forcing all 5-person teams is too large. Use a two-stage search: pre-rank candidates by role/purpose features and diversity, then beam-search / greedy-expand top pools into candidate 3–5 person teams. For 3-person teams, exhaustive search may be feasible after pre-filtering.
Reference: references/bg5-team-explorer-mvp.md documents the first HD Prism script MVP, commands, purpose presets, scoring dimensions, verification, and next API/UI extension path.
Use oc16-scale only when the question is about organizations, departments, or company structures rather than a 3–5 person team.
Current evidence is orientation-level only. The wiki page concepts/oc16.md says OC16 is a larger-group/organizational scale described by BG5BI as three Pentas plus a leader/alpha. Do not invent detailed OC16 graphing procedures until primary BG5/OC16 material is ingested.
Every non-obvious BG5/Penta/OC16 claim should cite one of:
{"base": "wiki-human-design", "page": "concepts/bg5"}
{"base": "wiki-human-design", "page": "concepts/penta"}
{"base": "wiki-human-design", "page": "concepts/oc16"}
{"base": "wiki-human-design", "page": "queries/bg5-research-deep-dive-report"}
Chart-mechanics claims cite HD Prism implicitly by naming the source field in chart_facts.
When a compose/deep-dive layer weaves this lens into prose:
Good prose move:
Through the BG5 lens, this is less about finding a generic career label and more about protecting the material use of the design. The work path has to honor the same authority that governs the rest of the life; otherwise the Penta or organization can borrow the person’s energy for a structure that is not correct for them.
Calling one chart a Penta analysis. A Penta requires group data. With one person, call it an individual BG5/work lens.
Treating BG5 as generic career coaching. Keep it tied to HD Prism chart mechanics and the BG5/Penta source spine.
Skipping authority. Career/business questions are especially vulnerable to mental, practical, or social pressure. Authority remains the decision filter.
Inventing OC16 details. Current wiki evidence supports the scale model but not detailed OC16 procedure.
Over-citing in final prose. The lens should output citations; compose can decide whether to show them. If the user asks for sources, cite clearly.
Using astrology chart data as input. This is an HD lens. It consumes HD Prism bodygraph JSON, not natal astrology chart JSON.
concepts/bg5.md, concepts/penta.md, concepts/oc16.md, and/or the BG5 report were read.