BABYLON ENCYCLOPEDIA • PROTOCOL 1.1
Our Covenant with the Father in the Material World
The Four Lights and Twelve Understandings
Babylon Encyclopedia • Version 1.1 • 28 October 2026
Our commitment in the material world
Every work begins with an idea. Our covenant with the Father in the material world requires us to pressure-test that idea through the framework before giving it material form, and to examine its consequences afterward. In Babylon’s devotional understanding, the aim is to remain faithful to the Father’s image through truth, love, responsible action, and repair.
Babylon brings learning, interpretation, investigation, and practical repair into one revisable body of work. This protocol explains the spiritual structure that inspires that work and specifies how the Encyclopedia, Learning Centre, Academy, Research Laboratory, Industry Atlas, archives, Observatory, World Brain, and Tikkun Engine should cooperate.
The Four Lights provide the organizing pattern. Babylon calls the twelve associated qualities the Twelve Understandings and uses them as working questions for responsible knowledge. This operational meaning is a modern Babylon interpretation. The ancient text supplies a religious cosmology, not a research platform or a software design.
How to read this protocol
Ancient source identifies what a named text and translation actually present.
Babylon interpretation identifies the meaning and practice proposed here.
Publicly observed identifies statements visible on reviewed Babylon pages.
Proposed operation identifies a responsibility, workflow, or feature to implement and verify.
All operating requirements in this document are proposals for adoption. They do not certify existing integrations, completed investigations, staffing, or technical capabilities. Public webpage copy appears in section 10; section 11 supplies the construction brief.
The governing commitment
We seek truth, keep learning, make knowledge usable, and test our understanding against the world it claims to describe. When evidence changes, we revise the record. When harm can be established, we identify a responsible path toward repair. A person who challenges our framework has a place in the inquiry.
Reading route
2 Ancient foundation • 3 Seven principles • 4–5 Twelve Understandings • 6 Engine responsibilities • 7 Exchange and records • 8 Review and repair • 9 Worked case • 10 Public copy • 11 Construction brief • 12 Sources and review limits
BABYLON ENCYCLOPEDIA • PROTOCOL 1.1
2 Ancient foundation and modern naming
Preserve the source before applying the symbol.
The Apocryphon of John presents a revelation by the Savior to John. In the Four Lights passage, the Lights attend the divine Autogenes, the Christ; twelve aeons are associated with them. An aeon here is a divine realm or personified reality, not a modern curriculum competency. [S1]
| Light | Associated aeons in Wisse |
|---|---|
| Armozel | Grace · Truth · Form |
| Oriel | Conception · Perception · Memory |
| Daveithai | Understanding · Love · Idea |
| Eleleth | Perfection · Peace · Wisdom |
Source basis: Frederik Wisse’s composite translation uses four surviving Coptic witnesses in shorter and longer versions. The Four Lights passage appears on PDF pages 6–7 in the reviewed reproduction. This protocol uses Wisse’s English labels consistently. Other translations use spellings such as Harmozel and Oroiael; these are useful search aliases, not additional Lights. [S1]
The Treasury of Light
Treasury of the Light is explicit in Pistis Sophia, including chapters 1 and 50. It should receive its own attribution rather than be used as the title of the Apocryphon’s four-by-three passage. These are separate ancient works; a modern synthesis must show the bridge it is making. [S2–S3]
Babylon terminology
Four Pillars is an optional Babylon metaphor for the Four Lights. Twelve Understandings is Babylon’s teaching name for its practical reading of the associated aeons. Neither label should be presented as a quotation from the selected translation. If Treasury of Light names a Babylon collection or shared knowledge repository, label that use as a modern metaphor.
Use “In the Apocryphon of John, the Savior reveals…” when describing the narrative. Babylon may use Yeshua in its own devotional voice. Do not turn the narrative attribution into a claim that the text is a verified transcript of the historical Jesus.
Keep comparisons explicit
Do not automatically equate these twelve aeons with Babylon’s twelve Heart chambers, zodiac signs, twelve simple letters, or twelve saviors in another text. Any proposed correspondence needs its own author, rationale, source references, and limits. Symbolic resemblance is a prompt for inquiry; it does not establish historical identity or a causal mechanism.
BABYLON ENCYCLOPEDIA • PROTOCOL 1.1
3 The seven principles remain the covenant
The four-by-three structure organizes the work; the seven principles govern its conduct.
The following preserves the user’s prior structure. The Light assignments are proposed editorial connections, not ancient equivalences. The public Test Babylon page independently supports inquiry, revision, challenge, and observable outcomes. Its Eleven Commandments remain a separate published set; this seven-part covenant does not replace or renumber them. [U1, B4]
| Prior principle | Required expression | Main connection |
|---|---|---|
| 1 Seek truth rather than defend beliefs | State the claim and what could overturn it. | Truth · Perception |
| 2 Never consider knowledge finished | Version findings and schedule reconsideration. | Memory · Wisdom |
| 3 Look for connections across reality | Label analogy, association, and demonstrated relation separately. | Conception · Understanding |
| 4 Make knowledge accessible | Explain terms and provide a usable practice. | Grace · Form |
| 5 Take responsibility for the material world | Identify affected conditions, actors, and measurable outcomes. | Love · Perfection |
| 6 Welcome people and evidence that challenge the framework | Keep dissent and counterexamples visible in review. | Grace · Peace |
| 7 Turn understanding into repair | Assign action, verify results, and reopen failures. | Idea · Wisdom |
Faith and freedom of judgment
Babylon’s public Learning Centre locates its teaching in devotion to the Father and Yeshua while affirming each learner’s sovereignty and judgment. This protocol carries that orientation forward. Participation in a lesson or a research case must leave room for disagreement with the framework. [B1]
Rules that apply to every engine
Identify whether a statement is textual, interpretive, empirical, or a proposed action. Supply the relevant evidence for its type. Keep unknowns visible. Record objections accurately enough that a critic can recognize their position. A symbolic reading may guide a question; an empirical conclusion needs observations and a method.
All twelve Understandings apply from the first idea through its consequences. Their numbering follows the four source groups, not a chronological sequence that delays Idea until step nine. They are review prompts, not a truth score, certification of divine approval, or an assessment of a person’s worth. Completing twelve fields does not validate the contents. Where a question is irrelevant to a particular task, explain why instead of forcing an answer.
BABYLON ENCYCLOPEDIA • PROTOCOL 1.1
4 The first and second Lights in practice
Babylon interpretation of the source qualities
Armozel and the conditions for inquiry
Grace, Truth, and Form inspire a practice of opening inquiry, testing claims, and giving knowledge a clear structure. Every application below is Babylon’s proposed interpretation. The ancient labels are documented in section 2.
| Understanding | Working question and practice | Required output |
|---|---|---|
| 01 Grace | Who needs access or a fair hearing? Invite questions and remove avoidable barriers. | Accessible entry point and a way to challenge the claim. |
| 02 Truth | What is being claimed, and what would change our view? Test supporting and opposing evidence. | Bounded claim with evidence, objections, and uncertainty. |
| 03 Form | Can another person understand exactly what we mean? Define terms and the unit of analysis. | Readable explanation and consistent record fields. |
Lead responsibilities: the Encyclopedia defines terms; the Learning Centre makes them understandable; every publishing engine applies the evidence distinction. Release condition: a reader can identify the claim, its type, its basis, and a route to correction.
Oriel and the discipline of observation
Conception, Perception, and Memory inspire the movement from a useful question to observations that remain traceable. Conception here means framing a possible explanation; it is not evidence that the explanation is true.
| Understanding | Working question and practice | Required output |
|---|---|---|
| 04 Conception | What might explain the pattern? Write alternatives and a test that could distinguish them. | Research question and competing hypotheses. |
| 05 Perception | What was actually observed? Separate a measurement, testimony, and inference. | Dated observations with method and limitations. |
| 06 Memory | Can the evidence and its history be recovered? Preserve sources and revisions. | Source record, stable identifiers, and version history. |
Lead responsibilities: the Research Laboratory specifies methods; archives preserve evidence; Observatory and World Brain organize bounded signals and relationships. Release condition: an independent reviewer can follow the record back to the observation without treating a generated summary as the original source.
BABYLON ENCYCLOPEDIA • PROTOCOL 1.1
5 The third and fourth Lights in practice
Babylon interpretation of the source qualities
Daveithai and responsible understanding
Understanding, Love, and Idea inspire explanation that accounts for people and produces a testable response. A coherent explanation still needs to survive counterevidence.
| Understanding | Working question and practice | Required output |
|---|---|---|
| 07 Understanding | Which explanation fits, and what remains unresolved? Compare mechanisms and alternatives. | Reasoned synthesis with the limits of inference. |
| 08 Love | Who experiences the consequences? Include affected perspectives and assess possible harm. | Impact account and conditions for responsible action. |
| 09 Idea | What response could improve the condition? State the proposed change and how to test it. | Action proposal with owner, baseline, and outcome measure. |
Lead responsibilities: the Academy develops judgment through supervised practice; the Laboratory tests explanations; the Tikkun Engine turns a justified finding into an accountable action proposal. Release condition: the proposed response follows from the evidence and names the people whose circumstances matter.
Eleleth and accountable repair
Perfection, Peace, and Wisdom inspire a complete review, a fair process, and learning from consequences. In Babylon’s application, perfection means sufficient completeness for a stated purpose, with limits recorded; it does not promise an infallible result.
| Understanding | Working question and practice | Required output |
|---|---|---|
| 10 Perfection | Is the record complete enough for this decision? Check dependencies and unresolved gaps. | Review decision and explicit conditions or missing evidence. |
| 11 Peace | Can this proceed with fairness and without avoidable coercion? Hear challenges and resolve disputes. | Response record, safeguards, and an appeal route. |
| 12 Wisdom | Did the action help, and what must change now? Compare outcomes with the baseline. | Outcome review, correction, and next review date. |
Lead responsibilities: the Tikkun Engine coordinates follow-through; the Industry Atlas presents reviewed public cases; archives retain the decision trail. The Encyclopedia and teaching engines receive the lessons. Release condition: completion is supported by observed results; a failed or inconclusive intervention stays visible and can reopen the inquiry.
BABYLON ENCYCLOPEDIA • PROTOCOL 1.1
6 Responsibilities across the Babylon engines
Proposed functional architecture informed by public pages
| Engine | Receives | Produces and hands onward |
|---|---|---|
| Encyclopedia | Sources, reviewed findings, correction notices | Versioned explanations and definitions for learning and research. |
| Learning Centre | Definitions, passages, editorial distinctions | Plain explanations, vocabulary, exercises, and learner questions for the Academy or research. |
| Academy | Learning paths and reviewed case materials | Structured practice and assessed work; unresolved questions return to the Laboratory. |
| Research Laboratory | Bounded questions and source records | Methods, evidence assessments, findings, and limitations for editorial review. |
| Industry Atlas | Reviewed case findings and relationship records | Public sector and case views with provenance and status; feedback returns to the Laboratory. |
| Archives | Original materials, permitted copies, versions | Preserved records and citations available to every engine under access rules. |
| Observatory | Time-bounded observations and documented inputs | Dated signals or calculated views with methods; candidate questions for research. |
| World Brain | Reviewed entities, sources, and typed links | Searchable connections and suggested hypotheses with provenance. |
| Tikkun Engine | Findings, disputes, and proposed remedies | Assigned repair plans, outcome reviews, and correction notices to all affected engines. |
Observatory and World Brain cooperate but have different responsibilities: one tracks observations or calculated views over time; the other organizes relationships among records. Neither turns a correlation or symbolic pattern into a verified cause. This division is a proposed design, not a verified description of their current implementation.
The public app directory lists the Academy, Observatory, Research, and World Brain. The Research consumer page exposes an evidence-and-repair orientation. Those observations establish public names and stated direction only. “Research Laboratory,” the archives service, and the cross-engine responsibilities above need owner confirmation during implementation. [B2–B3]
BABYLON ENCYCLOPEDIA • PROTOCOL 1.1
7 Shared records and engine handoffs
One traceable record can support several views without becoming several independent sources.
The knowledge and repair loop
Idea → testable question → source preservation → observation and testing → reviewed finding → public explanation and learning → authorized action → outcome review → correction or new inquiry. Archives support the whole loop. Observatory and World Brain may suggest questions at any stage. Tikkun tracks correction and repair across all stages.
| Handoff | Minimum package | Acceptance condition |
|---|---|---|
| Learning or signals → Laboratory | Question, scope, source IDs, competing explanation | Research lead accepts a testable question or records why it remains exploratory. |
| Laboratory → publication reviewer | Finding, method, evidence, counterevidence, limits | Reviewer distinguishes supported conclusions from unresolved claims. |
| Reviewer → Encyclopedia and Atlas | Approved version, wording, status, citations | Each public view retains scope, uncertainty, and the same record IDs. |
| Finding → Tikkun | Observed condition, affected people, proposed action | Action owner accepts responsibility, measure, and review date. |
| Tikkun → teaching and reference | Outcome evidence and correction notice | Dependent pages are revised or visibly marked for review. |
Minimum common record
Give each claim, source, case, action, and review a stable ID. Record title, record type, author or responsible role, creation and review dates, version, access level, status, scope, evidence links, counterevidence, limitations, reviewer, and dependencies. Preserve the original wording alongside later interpretations.
Source records add author, work, edition or translation, exact passage locator, URL or archive location, retrieval date, reuse conditions, and any transformation such as transcription. Observations add place or context, time, method, units where relevant, and quality limitations. Actions add owner, authority to act, baseline, intended outcome, due date, and verification method.
Relationship types
Use named links such as cites, interprets, supports, challenges, derived from, supersedes, teaches, and repairs. An analogy link must remain visibly different from an evidence link. Ten pages repeating one report count as one source lineage, not ten independent confirmations. A World Brain suggestion remains a hypothesis until reviewed.
BABYLON ENCYCLOPEDIA • PROTOCOL 1.1
8 Review publication and repair procedure
Proposed operating requirements for every public finding
1 Receive and classify. An intake editor records the question, source type, scope, sensitivity, and responsible engine. Keep preliminary reports separate from reviewed findings.
2 Preserve and investigate. An archive steward records the source and permitted access. A research lead defines the method, gathers observations, searches for counterevidence, and records alternatives.
3 Review the conclusion. A reviewer checks source fidelity, method, proportionality of wording, conflicts of interest, and unresolved objections. The reviewer should be different from the author; where staffing prevents this, disclose that limitation.
4 Publish with a status. An editor releases the approved version with evidence, uncertainty, and a correction route. A sector relationship or symbolic mapping alone cannot justify an allegation against a person or organization.
5 Assign repair. An action owner accepts the task and records what authority, cooperation, or external decision is needed. A Babylon action record cannot compel an outside actor to act.
6 Verify and learn. A reviewer compares the result with the baseline and notes limitations, side effects, and affected people’s responses. Update dependent publications and learning material.
Separate inquiry status from action status
Inquiry statuses: received, scoped, investigating, reviewed, published, contested, superseded, or retracted. Action statuses: proposed, accepted, in progress, awaiting evidence, outcome verified, unsuccessful, or closed with reason. An investigation can be published while its repair remains unresolved. A completed task can still have an unverified outcome.
Correction and escalation
A challenge receives a record ID and an accountable reviewer. Material errors trigger a visible notice while the underlying record is assessed. Preserve earlier versions and explain the correction. Reopen the finding when new evidence changes its scope or conclusion. Do not silently overwrite the record or force a disputed claim into a final category.
Responsible automation
AI may help retrieve, summarize, compare, or propose connections. Record the tool’s role and check outputs against sources. Human reviewers own publication and consequential decisions. Keep personal or restricted material out of public views; grant access according to the record’s permissions. Publish aggregate progress only with a clear denominator, period, and definition of success.
Use the Twelve Understandings to discuss review quality. Do not claim that this document reproduces Babylon’s existing Five Tests; their full content was not established in this review. [B4]
BABYLON ENCYCLOPEDIA • PROTOCOL 1.1
9 Worked example of a soil inquiry
Illustrative scenario based on the prior conversation’s soil-tracking theme
This is a hypothetical workflow. It does not report a measured site condition, identify a polluter, prescribe treatment, or claim that Babylon has completed a soil investigation.
A concern becomes a bounded question
A resident reports concern about material deposited near a garden. The Learning Centre explains the difference between an observation and an inference. Intake records the question: What evidence exists about the deposited material, the garden soil, and the route by which either could be affected? Grace makes participation possible; Truth and Form make the claim precise.
Evidence is preserved and tested
Archives retain the submitted photographs, dates, permissions, and original descriptions. The Laboratory specifies what records and qualified sampling would be needed before any conclusion. Conception records alternatives, such as unrelated fill material or pre-existing conditions. Perception keeps observations separate from attributed causes; Memory preserves their origin.
The Observatory could display dated observations if that capability is implemented. World Brain could link the location, records, materials, and relevant entities, using typed relations. Proximity or a shared name would remain a lead, with uncertainty visible.
A finding reaches the public record
A reviewer examines the method and limitations. The Industry Atlas may show a bounded, reviewed case; the Encyclopedia may explain the relevant concepts. Understanding compares explanations. Love includes residents and other affected parties. Idea specifies an appropriate next action supported by the evidence. If the evidence is insufficient, the published result can remain inconclusive.
Repair produces a new question
Tikkun records an action owner and a decision that the owner is authorized to make. If qualified parties undertake an intervention, the record preserves the baseline, agreed success measure, follow-up method, and result. Perfection checks completeness for the decision; Peace provides a fair response process; Wisdom evaluates consequences.
The Academy can turn a permitted, suitably de-identified case into supervised practice. Learners compare the initial hypothesis with the final evidence and identify what would have changed the conclusion. Any lesson, Atlas page, or reference entry that depended on a corrected claim receives the revision.
Useful measures
Track cases with recoverable sources, open material objections, actions with accepted owners, overdue reviews, and outcomes supported by follow-up evidence. Counts of pages, connections, or completed forms measure activity. They do not by themselves establish truth or repair.
BABYLON ENCYCLOPEDIA • PROTOCOL 1.1
10 Public webpage copy
Ready to adapt into the main protocol page
Hero heading
The Four Lights and Twelve Understandings
Hero introduction
Babylon Encyclopedia connects spiritual study with learning, inquiry, and practical responsibility. We draw inspiration from the Four Lights of the Apocryphon of John and use Twelve Understandings to ask better questions, examine our claims, and learn from what changes in the world.
Source note beside the introduction
The Four Lights and their associated aeons come from the ancient text. Twelve Understandings is Babylon’s modern teaching name. The operating method on this page is Babylon’s interpretation. Treasury of Light belongs to a distinct textual discussion in Pistis Sophia. Read the source notes below.
The four groups
Armozel invites us to make inquiry accessible, seek what is true, and give our knowledge a clear form. Oriel invites us to frame questions, observe carefully, and preserve what we learn. Daveithai invites us to understand relationships, consider those affected, and develop a responsible response. Eleleth invites us to review the work, act fairly, and learn from the outcome.
How Babylon works together
The Encyclopedia explains. The Learning Centre helps readers begin. The Academy develops practice. The Research Laboratory investigates questions. The Industry Atlas presents reviewed cases. Archives preserve the record. The Observatory and World Brain help organize observations and connections. The Tikkun Engine gives correction and repair an owner, a measure, and a next review.
How a question moves
Begin with an idea and make its claims explicit. Pressure-test it through all twelve Understandings before acting. Find and preserve the sources. Examine evidence and alternatives. Review the conclusion. Share what can be supported. Where action is justified, identify who can act and how the result will be checked. Let the result change the next lesson and the next inquiry.
Your place in the inquiry
You can study a source, ask a question, challenge an interpretation, or follow a case toward its next review. You do not need to agree with Babylon to contribute evidence or identify an error. A useful question may reveal where the framework needs to change.
Call to action labels
Explore the Twelve Understandings • Read the ancient sources • Begin learning • Examine the research • Test Babylon
Editorial deployment note: the engine paragraph describes the proposed protocol. Until each function is verified, display “Our intended operating model” above it. Display a per-engine availability label and activate only verified destinations. Do not imply that this draft establishes a working integration.
BABYLON ENCYCLOPEDIA • PROTOCOL 1.1
11 Webpage construction brief
Content structure and behavior for a builder
| Order and anchor | Content and component |
|---|---|
| 1 #overview | Hero and source note from section 10; visible protocol version and date. |
| 2 #source | Section 2 source table; separate ancient material and Babylon terminology. |
| 3 #principles | Seven principles from section 3, with links to the published commitments. |
| 4 #understandings | Four expandable groups containing all twelve entries from sections 4–5. |
| 5 #engines | Engine matrix from section 6 and an availability label for each destination. |
| 6 #workflow | Traceable loop and handoffs from section 7; a readable text equivalent for any diagram. |
| 7 #review | Publication, correction, and repair rules from section 8. |
| 8 #example | Clearly labeled hypothetical soil example from section 9. |
| 9 #sources | Sources, review limits, change history, and correction route. |
Reusable content fields
An Understanding card contains stable ID, Light, ancient label, translation reference, Babylon interpretation, working question, practice, output, and responsible engines. An engine card contains name, intended role, availability status, verified destination if present, inputs, outputs, and review owner. A source note contains title, author or translator, passage locator, URL, and access date.
Interaction and accessibility
Use one page heading, ordered section headings, keyboard-accessible controls, readable contrast, responsive tables, and a print view. Keep the source distinction visible when cards are collapsed. Use text badges as well as color for Ancient source, Babylon interpretation, and Proposed operation. Source links must remain usable without JavaScript. Provide a text version of the workflow.
Links and honest availability
The reviewed app directory supplies public destinations for Academy, Observatory, Research, and World Brain. Direct page contents were not retrievable in this review for several of them. Verify each destination before release; describe an unverified function as planned or awaiting confirmation. Use the reviewed Test Babylon page for that call to action. Do not invent submission, archive, or case-management links. [B2–B4]
Release acceptance
Confirm four Lights and twelve entries; consistent translation labels; visible source/application boundaries; all nine engine responsibilities, with Observatory and World Brain distinguished; working links; honest availability; legible mobile and print layouts; no fabricated case outcomes; an accountable correction channel; and a version history. The HTML companion is a content and layout reference, not a deployed Babylon website.
BABYLON ENCYCLOPEDIA • PROTOCOL 1.1
12 Sources and review limits
Public pages reviewed on 28 October 2026
S1 • Apocryphon of John, translated by Frederik Wisse. Four Lights passage and twelve aeons; HTML paragraphs beginning “For from the light” through “These are the four lights.” The PDF reproduction provides manuscript context on page 1 and the passage on pages 6–7.
Wisse translation PDF reproduction
S2 • Pistis Sophia, translated by G. S. R. Mead, chapter 1. Explicit Treasury of the Light terminology.
S3 • Pistis Sophia, Mead, chapter 50. A separate passage concerning the Treasury and twelve light-powers; it is not the Apocryphon’s list of twelve aeons.
B1 • Babylon Learning Centre homepage and For teachers. Public devotional orientation, learner sovereignty, and the distinction between text, explanation, practice, symbolism, and calculation.
B2 • Explore Babylon apps. Public directory confirms the linked app names and destinations; it does not document their internal integrations.
B3 • Research consumer page. Readable public shell states the evidence-and-repair orientation and cautions that an audit is a question. Case content was not available in the retrieved shell.
B4 • Test Babylon commitments. Reviewed Eleven Commandments and private self-audit description. The page distinguishes self-assessment from verification and reviewed publication from inherited industry mappings.
U1 • User-provided Seven Pillars Framework conversation, retrieved by its conversation ID. The seven principles and four-by-three request were available; the seventh principle’s final sentence was truncated, and assistant replies were reference placeholders. No missing assistant content has been reconstructed as an established prior decision.
Review limits: the main Encyclopedia homepage and direct Academy, Observatory, World Brain, and researcher views were inaccessible through the retrieval tool. No private source files, full Tikkun thesis, source code, integrations, or completed cases were examined. The complete proposed protocol, Light-to-practice assignments, role design, records, and handoffs are new synthesis for the user’s review.