334digital.com

Category: Guides

  • The Brontologicon — A Research Brief on the Medieval “Thunder Books”

    Question

    What is the Brontologicon? The term — along with its cognates brontologion (Greek), brontologia / brontologies (Latin), and the related practices of brontomancy and brontoscopy — refers to a genre of prognostication texts (“thunder books”) that interpret thunder and other celestial omens to forecast events. This brief maps the genre’s origins, structure, manuscript transmission, and the modern scholarship that has re-evaluated it.

    Executive Summary

    1. A genre, not a single canonical book. Brontologicon (Latinised from Greek βροντή, “thunder” + λόγος, “account/lore”) is the scholarly name for a family of texts — not one fixed work. The “-con” ending is modelled on Latin neuter titles such as Chronicon or Computicon (“book of…”).
    2. Logic of the genre. A brontologicon offers “sets of predictions for the year ahead when thunder events are heard, either during a calendar month or one of the twelve periods of the signs of the Zodiac.” It predicts politics, agriculture, weather, war, and health from observed thunder, eclipses, halos, and earthquakes.
    3. Ancient roots in Etruscan divination. The earliest surviving model is the Etruscan Brontoscopic Calendar — a day-by-day register of “if it thunders, then…” omens, attributed to the legendary prophet Tages and transcribed by the Roman scholar Nigidius Figulus (1st c. BCE); it survives through the Byzantine antiquarian John Lydus.
    4. A Pseudo-Bede centre of gravity in the Latin West. The most influential Latin brontologicon is the De tonitruis (De tonitruis libellus ad Herefridum), long attributed to the Venerable Bede. Modern scholarship (Charles W. Jones) showed the attribution is spurious. It is structured in a prologue plus four chapters on thunder heard (I) in each of four cardinal directions, (II) in each of twelve months, (III) on each of seven days of the week, and (IV) at hours of day and night.
    5. A pan-European tradition. Brontologia circulated in Latin, Middle English, Byzantine Greek, Slavonic, and Georgian, and were copied into medical/scientific manuscripts alongside computus tables, Easter reckonings, zodiac-man diagrams, and regimen sanitatis material.
    6. Rehabilitated by recent scholarship. Once dismissed as kleinliteratur (“lesser writings”) or folklore, brontologia are now treated as part of monastic learned culture, sitting at the border between licit prognostication and divination.

    Methodology

    This brief was built from public web search across three angles: (a) the genre term and its cognates (“brontologicon”, “brontologia”, “brontologion”, “brontomancy”); (b) the specific Latin flagship text “De tonitruis” and the Pseudo-Bede question; and (c) the ancient Etruscan origin and the Eastern/Byzantine and Georgian branches. Sources include peer-reviewed articles (Reading Medieval Studies, Journal for the History of Astronomy, Bryn Mawr Classical Review), a 2024 doctoral thesis (University of Reading), an academic handbook chapter (De Gruyter), a specialist press edition (Hadean Press), a manuscript catalogue (Morgan Library), and Wikipedia entries used only for orientation. Limitations: the page-fetching service was unavailable during research, so several claims rest on search snippets rather than full-text reading; dates of publication are noted where retrievable, and “-” is used where they are not. Where two independent sources corroborate a claim, that is flagged.

    Findings

    1. What the word means and why it is a genre

    The Greek βροντή (brontē, “thunder”) gives the combining root. A brontologion / brontologicon is literally a “thunder-account” or “book of thunder” — a manual that lets a reader convert an observed thunder event into a forecast. Modern scholars describe brontologia as “a popular genre of prognostication texts” that “predicted politics, agriculture, weather, and health based on the inquirer’s observations of thunder, eclipses, halos, earthquakes, and similar natural phenomena during the year” (source [1]). Closely allied terms: brontomancy (divination by thunder), brontoscopy (the act of observing thunder for omens), and ceraunoscopy (observing thunder and lightning).

    2. The ancient ancestor: the Etruscan Brontoscopic Calendar

    The deepest known root of the genre lies in the Etruscan libri fulgurales — books on divination by lightning and thunder. Seneca captures the Etruscan logic: “the Etruscans do not believe that things have meaning because they happen, but that they happen for the sole purpose of meaning” (Natural Questions II.32.2). Embedded in this tradition was a brontoscopic calendar that “proposed for each day of the year an interpretation of thunder and celestial manifestations” (source [9]).

    Its survival is a story of double translation. In the first century BCE, Cicero’s contemporary Nigidius Figulus transcribed a brontoscopic calendar attributed to the legendary Etruscan prophet Tages (source [10]). The Etruscan/Latin original is lost, but the text was translated into Greek by the Byzantine antiquarian John Lydus (De Ostentis), which is why it survives (source [10]). Each entry follows a fixed protasis–apodosis form — a date, then “ἐὰν βροντήσῃ” (“if it thunders…”), then the meaning of thunder on that day (source [11]). Jean Macintosh Turfa’s Divining the Etruscan World (Cambridge UP) is the standard modern edition and study (source [11]).

    3. The Latin flagship: De tonitruis and the Pseudo-Bede question

    In the medieval Latin West, the best-known brontologicon is De tonitruis (full title De tonitruis libellus ad Herefridum — “the little book on thunder to Herefrid”). It was transmitted under the name of the Venerable Bede, lending it authority in monastic libraries. Its structure is a prologue plus four chapters, dealing with the meaning of thunder heard:

    • (I) in each of the four cardinal directions;
    • (II) in each of the twelve months of the year;
    • (III) on each of the seven days of the week;
    • (IV) at certain hours of the day and of the night (source [5]).

    The Bede attribution is spurious. Charles W. Jones, who first discussed the text in detail, “convincingly dismissed the attribution to Bede and identified what he thought to be the only extant MS (and also the exemplar used by Noviomagus): Cologne, Erzbischöfliche Diözesan- und Dombibliothek, 102” (source [5]). The first English translation of the Latin De Tonitruis was published by Hadean Press under the title Brontomantia, framing it as “prognostication of the future based on the observation of thunder” (source [6]).

    A typical late-medieval forecast reads like the example preserved in the tradition: “if they heard thunder in January there was likely to be strong winds, abundant crops, and much bloodshed in the year to come” (source [4]).

    4. The genre in practice: months, zodiac, and “thunder books”

    Not all brontologia key on the calendar month. Some — explicitly noted as an exception in the literature — “offer predictions based on the combination of hearing thunder with a specific sign of the zodiac, or month of the year” (source [7]). This is the form Walls describes: predictions keyed to “a calendar month or one of the twelve periods of the signs of the Zodiac” (source [3]). The Middle English vernacular descendants were known colloquially as “thunder books” (source [2]).

    5. Manuscript context: where brontologia lived

    Brontologia were not isolated texts. They were copied into computus and medical/scientific compilations. The Walls thesis traces them “in English medical and scientific manuscripts, from the mid-thirteenth century to the first half of the sixteenth century” (source [3]). A 2021 article in Reading Medieval Studies (47:153–72) maps “The Relationship of Brontology and the Regimen of Health,” showing that brontologia often sat in the same booklet as applied astrology, zodiac-man diagrams, and planetary material (source [2]).

    Specific manuscript examples:

    • British Library Harley 978 — contains the De tonitruis alongside other prognostics dubiously attributed to Bede (De signis et horis xii mensium, De nativitate infantium libellus, De minutione sanguinis / de phlebotomia). An article on this manuscript frames the central interpretive question as “Prognostics: monastic divination or licit guidance?” (source [8]).
    • Morgan Library MS M.941 — an almanac with “12 pictures illustrating the months of the year, with thunder prognostications,” plus a Vein Man diagram with signs of the Zodiac and a circular diagram with God at centre (source [12]).
    • Thorney Abbey computus MS (c. 1110) — Easter tables, texts from Bede, Byrhtferth’s computus, astronomical materials, world maps, and the prognostic Revelatio text, illustrating how prognostics were embedded in learned computistical works (source [13]).

    Earlier twentieth-century scholars “treated the brontology separately” from the broader compilations of astromedicine and practical science, “terming them kleinliteratur (‘lesser writings’)” (source [2]) — a dismissive label recent scholarship rejects.

    6. The Eastern and Georgian branches

    The genre was not confined to the Latin West. Michael Grünbart’s chapter “The Importance of Thunder: Brontologia in the Medieval Eastern Christian World” in Prognostication in the Medieval World: A Handbook (De Gruyter, 2021, pp. 811–813) maps the Byzantine and Eastern Christian transmission (source [14]).

    A notable Eastern example is MS A-620, a Georgian brontologion, studied as “Cultural and historical astronomy in a brontologion from Georgia” (Journal for the History of Astronomy, 2021) (source [1]). The Georgian material shows the genre reaching the Caucasus, predicting politics, agriculture, weather, and health from celestial observations (source [1]).

    7. Why the genre endured

    Brontologia’s tenacity is striking: Walls’s thesis is explicitly titled “The tenacity of brontology in late-medieval England.” Three factors explain it:

    • Clerical/monastic legitimacy via pseudo-epigraphy. Attribution to Bede (and, in other texts, to Abbo of Fleury) gave prognostics a respectable patristic-style authority that smoothed over the tension with condemnation of divination (source [8], [13]).
    • Embeddedness in useful learned contexts. Because they were copied with computus, Easter tables, medical regimens, and zodiac-man diagrams, brontologia rode along with materially useful material rather than standing alone as “superstition” (source [2], [8]).
    • Flexibility of the keying system. Whether keyed to months, zodiac signs, weekdays, or hours, the same protasis–apodosis template could be re-skinned for different audiences and languages — Latin, English, Greek, Georgian, Slavonic (sources [1], [3], [14]).

    Source Notes

    SourceCredibilityLast updated
    [1] Chiu et al., “Cultural and historical astronomy in a brontologion from Georgia,” Journal for the History of Astronomy — ADS abstract4/52021
    [2] J. C. Walls, “The Relationship of Brontology and the Regimen of Health,” Reading Medieval Studies 47 (2021): 153–72 — Reading GCMS PDF5/52021
    [3] J. C. Walls, The tenacity of brontology in late-medieval England: the evidence of manuscripts, PhD thesis, University of Reading — CentAUR record5/52024
    [4] “Medieval Omens” — Medievalists.net3/52022
    [5] “The De tonitruis Attributed to Bede: An Early Medieval Treatise on Divination by Thunder…” — ResearchGate4/5–
    [6] Brontomantia: Prognostication by Thunder — Hadean Press3/5–
    [7] Juste & Chiu, “De tonitruis,” referenced in International Journal of Divination and Prognostication article — research-portal.uu.nl PDF4/5–
    [8] “Prognostics: monastic divination or licit guidance? The case of Harley 978” — CentAUR PDF4/5–
    [9] “Black skulls and ‘Libri Fulgurales’” — civilisationsanciennes.org3/5–
    [10] “The Etruscan Brontoscopic Calendar and Modern Archaeological Discoveries” (J. M. Turfa) — Academia.edu4/5–
    [11] Review of Divining the Etruscan World (J. M. Turfa, Cambridge UP) — Bryn Mawr Classical Review5/52013
    [12] “Almanac and calendar, with thunder prognostications (MS M.941.1-3)” — The Morgan Library & Museum5/5–
    [13] “Weather Prognostics in Anglo-Saxon England” — Academia.edu4/5–
    [14] M. Grünbart, “The Importance of Thunder: Brontologia in the Medieval Eastern Christian World,” in Prognostication in the Medieval World: A Handbook (De Gruyter, 2021, pp. 811–813) — degruyterbrill.com5/52021

    Caveats. The page-fetching service was unavailable during this research, so several claims rest on search-result snippets rather than full-text inspection. The “abundant crops and bloodshed” forecast (source [4]) is a representative paraphrase of the genre’s logic, not a verbatim quotation from a specific named brontologicon. The term Brontologicon itself is a modern scholarly Latinisation; medieval texts more often bear titles like De tonitruis or are catalogued under brontologia / brontologion.

    Open Questions

    • Is there a single text specifically titled “Brontologicon”? No canonical medieval work bears that exact title; it is the generic name. A reader who expected a single famous “Brontologicon” should be told it names a genre whose flagship Latin instance is De tonitruis.
    • Origin of the Latin De tonitruis. Jones placed the Bede attribution in doubt and identified the Cologne exemplar, but the text’s pre-Bede source and date of composition remain debated.
    • The monastic-divination boundary. The Harley 978 study frames the key open historiographical question: were these texts read as illicit divinatio or as licit guidance, and did the distinction matter to their users?
    • Eastern ↔ Western exchange. Whether the Latin brontologia descend from the Etruscan/Byzantine brontoscopic calendar tradition or from a parallel astrological stream is not fully resolved.

    Recommendations

    1. Read the Walls thesis (2024) for the most current treatment of the Latin/Middle-English tradition; it is the foundational recent study.
    2. Consult Turfa, Divining the Etruscan World (2013) for the ancient ancestor and the protasis–apodosis form.
    3. Examine Morgan MS M.941 online to see a fully illustrated thunder-prognostication almanac and how the genre coexisted with zodiac and vein-man diagrams.

  • The Brontologicon — Summary, Description, and Examples

    Summary

    A brontologicon (from Greek βροντή, “thunder” + λόγος, “account/lore”) is a genre of prognostication text — a “thunder book” — that converts an observed thunder event into a forecast of the year ahead. It is not a single canonical work; the name (modelled on Latin neuter titles like Chronicon, “book of times”) is the modern scholarly label for a whole family of manuals.

    The genre’s logic is consistent across cultures: note when and where thunder is heard (which month, zodiac sign, weekday, hour, or cardinal direction), then look up the matching omen — typically about politics, warfare, agriculture, weather, plague, and health. Its deepest root is the Etruscan Brontoscopic Calendar (attributed to the prophet Tages, surviving via John Lydus). Its most influential medieval Latin instance is the De tonitruis (libellus ad Herefridum), long — but falsely — attributed to the Venerable Bede. Brontologia circulated in Latin, Greek, Aramaic, Georgian, and Middle English, and were copied into monastic computus and medical manuscripts alongside Easter tables, zodiac-man diagrams, and regimen sanitatis material. Once dismissed as kleinliteratur (“lesser writings”), the genre has been rehabilitated by recent scholarship as part of learned monastic prognostication.

    Description

    What it does

    A brontologicon is a lookup table of omens. The reader observes a thunder event and identifies its “key” — the calendar month, the zodiac sign the sun is in, the day of the week, the canonical hour, or the cardinal direction the sound comes from. The matching entry then states what that thunder means for the coming year. Crucially, brontologia interpret thunder as divinely meaningful, not random — Seneca’s famous line on the Etruscans captures the worldview: “they do not believe that things have meaning because they happen, but that they happen for the sole purpose of meaning.”

    Key variants and their “keying” systems

    VariantOrigin / eraHow thunder is keyed
    Etruscan Brontoscopic CalendarEtruscan → Roman (1st c. BCE, via Nigidius Figulus)Day of the year (365+ entries)
    De tonitruis (Pseudo-Bede)Early medieval Latin4 cardinal directions × 12 months × 7 weekdays × 11 hours
    Qumran Brontologion (4Q318)Aramaic, c. 1st c. BCE–1st c. CEWhere in the heavens thunder is heard, combined with a selenedromion (moon-zodiac) scheme
    Georgian “Signs of the Times” (MS A-620)17th-c. GeorgianMonth (predictions for Jan, Feb, Apr, May, etc.)
    Byzantine / Berlin brontologionByzantine GreekDay of the month, attributed to “the prophet Daniel”

    The flagship Latin text: De tonitruis

    The De tonitruis (or De tonitruis libellus ad Herefridum — “the little book on thunder to Herefrid”) is a short text of a prologue plus four chapters, dealing with the meaning of thunder heard:

    1. (I) in each of the four cardinal directions;
    2. (II) in each of the twelve months of the year;
    3. (III) on each of the seven days of the week;
    4. (IV) at certain hours of the day and of the night — specifically eleven canonical hours: day (first, third, sixth, ninth, tenth, twelfth), then night (dusk, first vigil, middle of the night, twilight, dawn).

    The Bede attribution is spurious. Charles W. Jones convincingly dismissed it and identified the likely exemplar as Cologne, Erzbischöfliche Diözesan- und Dombibliothek, 102. The text was first printed among Bede’s works by Noviomagus (Cologne, 1537) and reprinted in Migne’s Patrologia Latina. Modern scholarship (Juste & Chiu, Traditio 68, 2013) argues it was translated from Irish into Latin — making it among the earliest medieval Latin divination texts. Its first standalone English translation was published by Hadean Press as Brontomantia: Prognostication by Thunder.

    Where the texts lived

    Brontologia were not standalone “superstition” booklets. They were copied into monastic computus and medical/scientific compilations:

    • British Library Harley 978 — De tonitruis alongside other pseudo-Bede prognostics (on the signs and hours of the twelve months, on the nativity of infants, on bloodletting). An article on the manuscript poses the central question: “Prognostics: monastic divination or licit guidance?”
    • Morgan Library MS M.941 — an almanac with twelve month pictures with thunder prognostications, plus a Vein Man diagram with zodiac signs and a circular diagram with God at the centre.
    • Thorney Abbey computus MS (c. 1110) — Easter tables, Bede, Byrhtferth’s computus, world maps, and the prognostic Revelatio text.

    The genre survived because pseudo-epigraphy (Bede, Abbo of Fleury) gave it clerical legitimacy, and because it rode along inside materially useful learned compilations. Janet Walls’s 2024 Reading thesis, The tenacity of brontology in late-medieval England, traces this persistence from the mid-thirteenth to the mid-sixteenth century.

    Examples

    The following are real, sourced omen-entries that show the genre’s protasis–apodosis form (“if it thunders…, then…”). They are reproduced from secondary sources; wording in the original manuscripts varies.

    1. Etruscan Brontoscopic Calendar (keyed by day of the year)

    Each of the calendar’s entries is a date followed by a protasis (ἐὰν / εἰ βροντήσῃ — “if it thunders”) and an apodosis (the meaning). A representative entry:

    June 1 — If it thunders, there will be a destruction of crops, except barley.

    (Sourced via Turfa’s lecture and the published calendar; the full text runs to one omen per day of the year.) The calendar survives because Nigidius Figulus transcribed it (1st c. BCE) and John Lydus translated it into Greek in his De Ostentis (Byzantine, age of Justinian).

    2. De tonitruis (Pseudo-Bede) — keyed by month

    The month chapter gives a forecast for thunder heard in each calendar month. The pattern is clearly adverse in winter, favourable in late autumn:

    January — thunder predicts mortalities (death).
    December — thunder forecasts health and prosperity.

    A representative late-medieval English descendant of the same logic puts it as: “if they heard thunder in January there was likely to be strong winds, abundant crops, and much bloodshed in the year to come.”

    3. De tonitruis — keyed by canonical hour

    The hour chapter covers eleven monastic hours. Predictions are tied to the liturgical day: thunder at the first hour of the day, the third, the sixth, the ninth, the tenth, the twelfth, then at dusk, the first vigil, the middle of the night, twilight, and dawn — each carrying its own omen. (Specific apodoses per hour are given in the Juste & Chiu edition, Traditio 68, 2013, and Chardonnens, Anglo-Saxon Prognostics.)

    4. Qumran Brontologion (4Q318) — keyed by where in the heavens

    The Dead Sea Scrolls Aramaic text (4Q318) is the most intriguing variant: it is simultaneously a brontologion, a selenedromion, and a thema mundi. Here the key is where within the heavens the thunder is heard, cross-referenced with the zodiacal position of the moon. It shows the genre reaching Jewish Palestine by the turn of the era.

    5. Georgian brontologion “Signs of the Times” (MS A-620) — keyed by month

    A 17th-century Georgian brontologion entitled Signs of the Times preserves predictions for each month (folios cover January–February and April–May, with a missing folio between them). It predicts politics, agriculture, weather, and health from thunder — the same four-fold concern as the Latin and Etruscan traditions, a millennium and a half later.

    6. Byzantine “Berlin brontologion” — keyed by day of the month, attributed to Daniel

    A Byzantine Greek brontologion (Petropolis) keys each omen to the day of the month on which thunder occurs. Its entries are framed as revelations of the prophet Daniel — omen 13 opens: “Ἐκ τῶν ἀποκαλύψεων τοῦ προφήτου Δανιήλ…” (“From the revelations of the prophet Daniel…”) — illustrating how the genre borrowed biblical authority the way the Latin West borrowed Bede’s name.

    A note on authenticity. The entries above are drawn from scholarly editions, lecture notes, and search snippets of peer-reviewed work (Turfa; Juste & Chiu; the Georgian MS study; the Qumran publication). Exact wording in the original manuscripts varies by copy; where a single verbatim entry is shown (e.g., the June 1 Etruscan omen), it is taken from a cited secondary source rather than the original MS. For authoritative full texts, consult Turfa, Divining the Etruscan World (Cambridge UP, 2013) and Juste & Chiu, “The De tonitruis libellus Attributed to Bede,” Traditio 68 (2013): 97–124.

  • THE ÜBER BIBLE

    A Comprehensive Content Index of All Sacred Texts, Apocrypha, Pseudepigrapha, and Related Writings

    PART I: THE HEBREW BIBLE / TANAKH

    The Jewish Canon (24 Books)

    Torah (The Law)

    1. Genesis — Creation, patriarchs, Joseph
    2. Exodus — Moses, the Exodus, Sinai covenant, Tabernacle
    3. Leviticus — Priestly laws, holiness code, sacrifices
    4. Numbers — Wilderness wanderings, census, Balaam
    5. Deuteronomy — Moses’ farewell speeches, covenant renewal

    Nevi’im (The Prophets)

    Former Prophets
    6. Joshua — Conquest and settlement of Canaan
    7. Judges — Pre-monarchic Israel, the judges cycle
    8. 1 Samuel — Samuel, Saul, David’s rise
    9. 2 Samuel — David’s reign, Bathsheba, succession
    10. 1 Kings — Solomon, divided kingdom, Elijah
    11. 2 Kings — Elisha, Assyrian and Babylonian conquests

    Latter Prophets
    12. Isaiah — Judgment and salvation oracles (1st, 2nd, 3rd Isaiah)
    13. Jeremiah — Prophecies of doom, the new covenant
    14. Ezekiel — Visions, temple restoration, dry bones
    15. The Twelve (Minor Prophets)
    – Hosea — Unfaithful Israel as adulterous wife
    – Joel — Day of the Lord, outpouring of Spirit
    – Amos — Social justice oracles
    – Obadiah — Judgment on Edom
    – Jonah — Prophet and the great fish
    – Micah — Bethlehem birth prophecy, justice
    – Nahum — Fall of Nineveh
    – Habakkuk — Theodicy, the righteous shall live by faith
    – Zephaniah — Day of the Lord, remnant
    – Haggai — Rebuild the temple
    – Zechariah — Messianic visions, apocalyptic
    – Malachi — Priestly corruption, Elijah’s return

    Ketuvim (The Writings)

    1. Psalms — Hymns, laments, royal and wisdom psalms
    2. Proverbs — Wisdom sayings of Solomon and others
    3. Job — The problem of suffering, theodicy
    4. Song of Songs — Erotic love poetry
    5. Ruth — Moabite ancestress of David
    6. Lamentations — Dirges over destroyed Jerusalem
    7. Ecclesiastes — Vanity of vanities, existential wisdom
    8. Esther — Deliverance of Jews in Persia
    9. Daniel — Court tales and apocalyptic visions
    10. Ezra-Nehemiah — Post-exilic restoration, law, walls
    11. 1 Chronicles — Genealogies, David’s reign retold
    12. 2 Chronicles — Solomon to exile, temple focus

    PART II: SECOND TEMPLE & INTERTESTAMENTAL TEXTS

    Jewish texts from the Persian through Hellenistic periods

    1. 1 Enoch (Ethiopic Enoch) — Astronomical, parabolic, dream visions, epistle; Watchers and Giants
    2. 2 Enoch (Slavonic Enoch) — Creation, Melchizedek, seven heavens
    3. 3 Enoch (Hebrew Enoch / Sefer Hekhalot) — Enoch as Metatron, heavenly palaces
    4. Book of Jubilees — Rewritten Genesis-Exodus, 49-year jubilee cycles, angelology
    5. Book of Biblical Antiquities (Liber Antiquitatum Biblicarum / Pseudo-Philo) — Rewritten Bible from Adam to David
    6. Psalms of Solomon — Hymns on Pompey’s invasion, messianic hope
    7. Sibylline Oracles — Jewish and Christian oracles in Greek hexameter
    8. Testament of the Twelve Patriarchs — Deathbed speeches, ethics, messianism
    9. Testament of Job — Patient Job’s final words, magical girdle
    10. Testament of Solomon — Solomon’s control of demons, temple construction
    11. Testament of Adam — Three hours of the day, generations, prophecy
    12. Testament of Abraham — Abraham’s refusal to die, judgment scene
    13. Testament of Isaac — Isaac’s piety and death
    14. Testament of Jacob — Jacob’s final blessings
    15. Testament of Moses (Assumption of Moses) — Moses’ secret teachings, end times
    16. Life of Adam and Eve (Apocalypse of Moses) — Expulsion, penitence, deaths of Adam and Eve
    17. Joseph and Aseneth — Conversion and marriage of Aseneth
    18. Jannes and Jambres — Egyptian magicians opposing Moses
    19. History of the Rechabites — Island of the blessed, ascetic community
    20. Eldad and Modad — Prophets in the wilderness
    21. Pseudo-Phocylides — Wisdom poem in Greek
    22. 3 Maccabees — Ptolemy IV and the Jews of Egypt
    23. 4 Maccabees — Philosophical discourse on reason and the passions
    24. Letter of Aristeas — Origin of the Septuagint translation
    25. Aristobulus — Philosophical interpretations of Torah
    26. 2 Baruch (Syriac Apocalypse of Baruch) — Baruch’s visions after Jerusalem’s fall
    27. 3 Baruch (Greek Apocalypse of Baruch) — Heavenly journey, cosmology
    28. 4 Baruch (Paraleipomena of Jeremiah) — Jeremiah and Abimelech in Babylon
    29. Apocalypse of Abraham — Abraham’s conversion, heavenly ascent, eschatology
    30. Apocalypse of Adam — Secret knowledge from Adam to Seth
    31. Apocalypse of Elijah — End-time prophecy
    32. Apocalypse of Sedrach — Dialogues on death and judgment
    33. Apocalypse of Zephaniah — Guided tour of the afterlife
    34. Prayer of Jacob — Mystical invocation
    35. Prayer of Joseph — Jacob as angel Israel
    36. Odes of Solomon — Early Christian/Jewish-Christian hymns
    37. Hellenistic Synagogal Prayers — Liturgical prayers preserved in Apostolic Constitutions
    38. More Psalms of David (Qumran) — Non-canonical psalms from the Dead Sea Scrolls

    PART III: THE SEPTUAGINT ADDITIONS (DEUTEROCANON / APOCRYPHA)

    Texts in the Greek Septuagint but not in the Hebrew canon

    1. Tobit — Pious Tobit, Sarah, and the angel Raphael
    2. Judith — Judith beheads Holofernes
    3. Additions to Esther — Six Greek expansions (dreams, prayers, edicts)
    4. Wisdom of Solomon — Wisdom theology, immortality, Exodus retold
    5. Sirach (Ecclesiasticus / Ben Sira) — Wisdom instruction, hymn to the fathers
    6. Baruch — Confession of sins, wisdom poem, consolation
    7. Letter of Jeremiah — Polemic against idolatry
    8. Additions to Daniel
      • Prayer of Azariah and Song of the Three Holy Children — Furnace prayer
      • Susanna — Daniel’s judicial wisdom
      • Bel and the Dragon — Exposé of idolatry
    9. 1 Maccabees — Hasmonean revolt and history
    10. 2 Maccabees — Martyrdom theology, temple rededication
    11. 1 Esdras (3 Esdras) — Alternative Ezra history, the three guards
    12. 2 Esdras (4 Esdras / Apocalyptic Esdras) — Ezra’s lament, eagle vision, messianic woes
    13. Prayer of Manasseh — Penitential prayer of the wicked king
    14. Psalm 151 — David’s election and victory over Goliath

    PART IV: ETHIOPIAN ORTHODOX BROADER CANON

    Unique to the Ge’ez tradition

    1. 1 Enoch (already listed; canonical in Ethiopia)
    2. Jubilees (already listed; canonical in Ethiopia)
    3. 4 Baruch (already listed)
    4. Rest of the Words of Baruch — Additional Baruchic material
    5. Book of the Covenant (Mäshafä Kidan) — Liturgical and legal text
    6. Book of the Order of the Church (Mäshafä Ser’at) — Ecclesiastical ordinances
    7. Joseph ben Gurion (Josippon) — Medieval Jewish history in Ge’ez

    PART V: THE NEW TESTAMENT

    The 27-Book Christian Canon

    The Gospels

    1. Matthew — Jewish-Christian gospel, five discourses, fulfillment formulas
    2. Mark — Earliest gospel, messianic secret, passion focus
    3. Luke — Salvation history, marginalized, travel narrative
    4. John — Logos hymn, signs, “I am” sayings, farewell discourses

    History

    1. Acts of the Apostles — Church from Jerusalem to Rome, Peter and Paul

    Pauline Epistles

    1. Romans — Systematic theology, justification by faith
    2. 1 Corinthians — Church problems, resurrection, love chapter
    3. 2 Corinthians — Paul’s defense of his apostleship
    4. Galatians — Freedom from the law, fruit of the Spirit
    5. Ephesians — Church as Christ’s body, spiritual warfare
    6. Philippians — Joy in suffering, Christ hymn
    7. Colossians — Christ as cosmic head, household codes
    8. 1 Thessalonians — Eschatology, parousia of Christ
    9. 2 Thessalonians — Man of lawlessness, don’t be alarmed
    10. 1 Timothy — Church order, qualifications of leaders
    11. 2 Timothy — Paul’s final charge, Scripture inspiration
    12. Titus — Crete, sound doctrine
    13. Philemon — Onesimus, slavery and brotherhood
    14. Hebrews — Christ as high priest, Melchizedek, faith chapter

    General (Catholic) Epistles

    1. James — Faith and works, control of the tongue
    2. 1 Peter — Suffering as Christian, household codes
    3. 2 Peter — False teachers, delayed parousia
    4. 1 John — God is love, tests of true faith
    5. 2 John — Walk in truth, reject false teachers
    6. 3 John — Hospitality and Diotrephes
    7. Jude — Contend for the faith, Enoch quotation

    Apocalypse

    1. Revelation (Apocalypse of John) — Seven churches, seals, trumpets, bowls, New Jerusalem

    PART VI: NEW TESTAMENT APOCRYPHA — GOSPELS

    Alternative accounts of Jesus’ life and teachings

    1. Gospel of Thomas — 114 sayings of Jesus, no narrative
    2. Gospel of Philip — Valentinian sacramental theology
    3. Gospel of Truth — Valentinian meditation on ignorance and knowledge
    4. Gospel of Mary — Mary Magdalene’s secret teachings, conflict with Andrew and Peter
    5. Gospel of Judas — Judas as the only disciple who truly understands Jesus
    6. Gospel of Peter — Anti-Jewish passion narrative, talking cross
    7. Gospel of the Egyptians — Encratite sayings, Salome
    8. Gospel of the Hebrews — Jewish-Christian gospel, “my mother the Holy Spirit”
    9. Gospel of the Nazarenes — Aramaic/Hebrew Matthew traditions
    10. Gospel of the Ebionites — Vegetarian Jesus, anti-sacrificial
    11. Gospel of Basilides — Gnostic gospel (lost, known through references)
    12. Gospel of Marcion — Edited Luke, demiurge theology
    13. Gospel of Eve — Gnostic fragments on ascent
    14. Gospel of Perfection — Gnostic gospel (lost)
    15. Gospel of the Twelve — Alternative apostolic gospel (lost)
    16. Gospel of the Four Heavenly Regions — Cosmic gospel (lost)
    17. Gospel of the Savior — Coptic passion and resurrection fragments
    18. Secret Gospel of Mark — Extended Mark with mystical initiation (disputed authenticity)
    19. Infancy Gospel of James (Protevangelium of James) — Mary’s birth, virginity, nativity
    20. Infancy Gospel of Thomas — Boy Jesus’ miracles and mischief
    21. Arabic Infancy Gospel — Childhood miracles, magi, travels to Egypt
    22. History of Joseph the Carpenter — Death and glorification of Joseph
    23. Gospel of Nicodemus (Acts of Pilate) — Trial, descent into Hades, resurrection
    24. Gospel of Bartholomew — Dialogues in the underworld
    25. Questions of Bartholomew — Apostle’s inquiries into divine mysteries
    26. Gospel of the Lots of Mary — Divinatory text attributed to Mary

    PART VII: NEW TESTAMENT APOCRYPHA — ACTS

    Apostolic adventures beyond the canonical Acts

    1. Acts of Paul — Paul and Thecla, lion baptism, martyrdom
    2. Acts of Peter — Quo vadis, dog Simon Magus, crucifixion upside-down
    3. Acts of John — Lycomedes portrait, bedbugs, temple collapse, mystical discourses
    4. Acts of Andrew — Maximilla’s chastity, Matthias’ rescue, martyrdom on X-cross
    5. Acts of Thomas — Twin Jesus, India mission, bridal chamber hymn
    6. Acts of Philip — Slayer of dragons, conversion of the eunuch
    7. Acts of Barnabas — Cyprus mission, martyrdom
    8. Acts of Timothy — Martyrdom at Ephesus
    9. Acts of Titus — Crete mission
    10. Acts of Xanthippe and Polyxena — Chaste women and Paul
    11. Acts of Peter and Paul — Joint martyrdom in Rome
    12. Acts of Peter and the Twelve Apostles — Nag Hammadi merchant tale
    13. Acts of Paul and Thecla — Thecla’s independence and preaching
    14. Martyrdom of Paul — Beheading at Rome
    15. Martyrdom of Peter — Crucifixion upside-down
    16. Martyrdom of Andrew — X-shaped cross
    17. Martyrdom of Thomas — Spear martyrdom in India
    18. Ascension of Isaiah — Isaiah’s martyrdal vision, heavenly ascent, Beloved descent

    PART VIII: NEW TESTAMENT APOCRYPHA — EPISTLES

    Letters beyond the canonical 21

    1. Epistle of the Apostles — Post-resurrection dialogues, anti-Gnostic
    2. 3 Corinthians — Paul’s response to Simon and Cleobius
    3. Correspondence of Paul and Seneca — 14 letters (pious fiction)
    4. Epistle to the Laodiceans — Summary of Pauline themes (forged)
    5. Epistle of Barnabas — Allegorical interpretation, two ways
    6. Epistle to Diognetus — Apology, “the soul in the body”
    7. Didache (Teaching of the Twelve Apostles) — Two ways, liturgy, church order
    8. Shepherd of Hermas — Visions, mandates, similitudes; repentance
    9. 1 Clement — Corinthian schism, apostolic succession
    10. 2 Clement — Sermon on purity and repentance
    11. Ignatius of Antioch — 7 Authentic Epistles
      • To the Ephesians, Magnesians, Trallians, Romans, Philadelphians, Smyrnaeans, Polycarp
    12. Ignatius — Spurious Epistles
      • To the Tarsians, Antiochenes, Hero, Philippians, Mary of Cassobola
    13. Polycarp to the Philippians — Faith and love, Ignatius
    14. Martyrdom of Polycarp — Proto-martyrology, Eucharistic theology

    PART IX: NEW TESTAMENT APOCRYPHA — APOCALYPSES

    Revelations beyond John

    1. Apocalypse of Peter — Guided tours of heaven and hell (influential on Dante)
    2. Apocalypse of Paul — Vision of heaven’s gates, hell’s punishments
    3. Apocalypse of Thomas — Seven days before the end
    4. Apocalypse of Stephen — Stephen’s martyrdom and vision
    5. Apocalypse of the Virgin — Mary’s vision of the damned
    6. Questions of Ezra — Dialogues on death and judgment
    7. Vision of Ezra — Punishments and rewards
    8. Revelation of Esdras — Eschatological visions
    9. Testament of Adam — Three hours, generations to come
    10. Testament of Abraham — Death refused, judgment throne
    11. Testament of Isaac — Piety and death
    12. Testament of Jacob — Final blessings
    13. Testament of Job — Patience, magical girdle, daughters’ inheritance
    14. Testament of Solomon — Demonology, temple building
    15. Testament of the Twelve Patriarchs — Ethical testaments
    16. Testament of Moses (Assumption of Moses) — Secret teachings, eschaton
    17. Life of Adam and Eve — Expulsion, penitence, deaths

    PART X: THE NAG HAMMADI LIBRARY

    Gnostic and related texts from Upper Egypt (c. 350–400 CE)

    Gnostic Gospels and Revelatory Dialogues

    1. Apocryphon (Secret Book) of John — Creation myth, Pleroma, demiurge Yaldabaoth
    2. Gospel of Thomas (already listed)
    3. Gospel of Philip (already listed)
    4. Gospel of Truth (already listed)
    5. Gospel of the Egyptians (already listed)
    6. Gospel of Mary (already listed)
    7. Dialogue of the Savior — Savior’s final teachings to disciples
    8. Book of Thomas the Contender — Twin’s secret words
    9. Treatise on the Resurrection — Letter to Rheginus on spiritual resurrection
    10. Tripartite Tractate — Valentinian cosmology and soteriology
    11. Apocryphon of James — Secret book of James, secret book of John
    12. Apocalypse of Adam — Secret knowledge from Adam to Seth
    13. Hypostasis of the Archons — Rulers of darkness, spiritual rescue
    14. On the Origin of the World — Cosmogony and eschatology
    15. Exegesis on the Soul — Soul’s fall and restoration as feminine

    Sethian and Platonizing Texts

    1. Apocalypse of Adam (already listed)
    2. Zostrianos — Heavenly ascent through aeons
    3. Allogenes — Stranger’s ascent to the Unknowable One
    4. Three Steles of Seth — Seth’s hymns to the divine
    5. Marsanes — Platonizing ascent text
    6. Melchizedek — Heavenly Melchizedek as Christ-figure
    7. Thought of Norea — Norea, daughter of Eve, and the archons
    8. Trimorphic Protennoia — Three forms of First Thought

    Valentinian Texts

    1. Gospel of Truth (already listed)
    2. Tripartite Tractate (already listed)
    3. Treatise on the Resurrection (already listed)
    4. A Valentinian Exposition — Commentary on Valentinian myth
    5. Interpretation of Knowledge — Ecclesiology and sacraments

    Other Nag Hammadi Treatises

    1. Thunder, Perfect Mind — Divine feminine self-revelation
    2. Sophia of Jesus Christ — Questions of disciples, revelation of Sophia
    3. Concept of Our Great Power — Three ages of history
    4. Discourse on the Eighth and Ninth — Hermetic initiation dialogue
    5. Prayer of Thanksgiving — Hermetic prayer
    6. Asclepius 21–29 — Hermetic treatise on god and matter
    7. Paraphrase of Shem — Cosmology of Shem
    8. Second Treatise of the Great Seth — Seth’s revelation of the true Christ
    9. Teachings of Silvanus — Wisdom instruction
    10. Testimony of Truth — Anti-ecclesiastical polemic
    11. Sentences of Sextus — Pythagorean/Christian wisdom
    12. Eugnostos the Blessed — Letter on the divine realm
    13. Wisdom of Jesus Christ — Dialogue on the Pleroma
    14. Letter of Peter to Philip — Commission and ascent
    15. Acts of Peter and the Twelve Apostles — Lithargoel the pearl merchant

    PART XI: THE DEAD SEA SCROLLS — NON-BIBLICAL TEXTS

    Qumran sectarian and parabiblical literature (c. 250 BCE – 68 CE)

    Sectarian Rule Texts

    1. Community Rule (1QS / 4QS) — Sectarian organization, two spirits, covenant
    2. Damascus Document (CD / 4QD) — Exile, new covenant, laws
    3. War Scroll (1QM / 4Q491-496) — End-time battle between sons of light and darkness
    4. Temple Scroll (11QT) — Rewritten Torah, ideal temple
    5. Some of the Works of the Torah (4QMMT) — Halakhic letter to Jerusalem authorities
    6. Rule of the Congregation (1QSa) — Messianic banquet rules
    7. Rule of the Benedictions (1QSb) — Priestly blessings

    Pesharim (Biblical Commentaries)

    1. Pesher on Habakkuk (1QpHab) — Interpretation of Habakkuk for the sect
    2. Pesher on Nahum (4QpNah) — Kittim, Lion of Wrath
    3. Pesher on Psalms (4QpPsa, 4QpPsb) — Davidic messianism
    4. Pesher on Isaiah (4QpIsaa-f) — Multiple Isaiah commentaries
    5. Pesher on Hosea (4QpHosa, 4QpHosb) — Unfaithful Israel
    6. Pesher on Micah (1QpMic) — End-time ruler
    7. Pesher on Zephaniah (1QpZeph) — Day of the Lord
    8. Pesher on Malachi (5QpMal) — Messenger and covenant

    Hymnic and Poetic Texts

    1. Thanksgiving Hymns (1QH / 4QH) — Hymns of the Teacher of Righteousness
    2. Songs of the Sabbath Sacrifice (4Q400-407, 11Q17) — Angelic liturgy for 13 Sabbaths
    3. Words of the Luminaries (4Q504-506) — Daily prayers for the week
    4. Barkhi Nafshi (4Q434-438) — Bless the Lord, O my soul
    5. Non-Canonical Psalms (4Q380, 4Q381) — Psalms not in the biblical book

    Calendrical and Astronomical Texts

    1. Calendrical Documents (4Q320-325) — 364-day solar calendar
    2. Astronomical Enoch (4Q208-211) — Lunar phases and Enochic astronomy
    3. Horoscopes (4Q186) — Physiognomic astrology
    4. Brontologion (4Q318) — Thunder omens

    Wisdom Texts

    1. Instruction on the Two Spirits (1QS III-IV) — Cosmic dualism
    2. Instruction (4Q415-418, 4Q423) — Wisdom for the sectarian community
    3. Mysteries (1Q27, 4Q299-301) — Cosmic and eschatological secrets
    4. Ways of Righteousness (4Q420-421) — Ethical instruction
    5. Wiles of the Wicked Woman (4Q184) — Personified folly
    6. Beatitudes (4Q525) — Macarisms on wisdom

    Apocryphal and Parabiblical Texts

    1. Genesis Apocryphon (1Q20) — Expanded Genesis narratives in Aramaic
    2. Book of Giants (1Q23-24, 2Q26, 4Q203, 4Q530-533, 6Q8) — Enochic giant narratives
    3. Pseudo-Ezekiel (4Q385, 4Q386, 4Q388, 4Q391) — Ezekielic visions and resurrection
    4. Pseudo-Daniel (4Q243-245) — Danielic court tales
    5. Pseudo-Jubilees (4Q225-227) — Jubilees-related narratives
    6. Aramaic Levi Document (4Q213-214) — Levi’s priestly instruction and ascent
    7. Testament of Qahat (4Q542) — Kohath’s testament to Amram
    8. Visions of Amram (4Q543-549) — Amram’s vision of two angels
    9. Prayer of Enosh (4Q369) — Prayer of the patriarch Enosh
    10. Apocryphon of Moses (4Q375, 4Q376, 4Q408) — Moses-related legal texts
    11. Apocryphon of Joshua (4Q378-379, 4Q522, 4Q123) — Joshua narratives
    12. Apocryphon of Samuel-Kings (6Q9) — Historical narratives
    13. Apocryphon of Jeremiah (4Q383, 4Q384, 4Q385a, 4Q387, 4Q388a, 4Q389, 4Q390) — Jeremiah’s prophecies for the end times
    14. Pseudo-Moses (4Q385a, 4Q387-390) — Moses as eschatological prophet
    15. Birth of Noah (4Q534-536) — Noah’s miraculous birth and destiny
    16. Words of Michael (4Q529, 6Q23) — Angelic revelation through Michael
    17. New Jerusalem (1Q32, 2Q24, 4Q554-555, 5Q15, 11Q18) — Vision of the heavenly temple-city
    18. Copper Scroll (3Q15) — Treasure list, possibly sectarian or legendary

    Florilegia and Testimonia

    1. Florilegium (4Q174) — Messianic collection of biblical texts
    2. Testimonia (4Q175) — Collection of messianic proof texts
    3. Catena (4Q177) — Chain of biblical interpretations
    4. Melchizedek (11Q13) — Melchizedek as heavenly savior and jubilee

    PART XII: SAMARITAN SCRIPTURES

    Texts of the Samaritan Israelite community

    1. Samaritan Pentateuch — Torah with Samaritan textual variants
    2. Samaritan Book of Joshua (Tulida) — Conquest from Samaritan perspective
    3. Memar Markah (Tafsir) — Samaritan Aramaic targum and theology
    4. Defter — Samaritan liturgical collection
    5. Asatir (Samaritan Book of Secrets) — Pseudo-biblical history
    6. Chronicle of Joshua — Samaritan historical chronicle
    7. Chronicle Adler — Medieval Samaritan chronicle
    8. Book of the Secrets of Moses — Samaritan mystical text

    PART XIII: SYRIAC AND EARLY ORIENTAL TRADITIONS

    Texts from Syriac Christianity and related traditions

    1. Peshitta — Standard Syriac translation of the Bible
    2. Curetonian Gospels — Old Syriac gospel manuscript
    3. Sinaitic Palimpsest — Old Syriac gospels from St. Catherine’s
    4. Diatessaron of Tatian — Harmony of the four gospels
    5. Doctrine of Addai — Legend of Thaddaeus and Abgar of Edessa
    6. Teaching of the Apostles — Syriac church order
    7. Acts of Judas Thomas — Thomas in India, Hymn of the Pearl
    8. Book of the Laws of the Countries — Bardaisan’s dialogue on fate
    9. Dialogue on Fate — Free will and determinism
    10. Apology of Aristides — Early apology preserved in Syriac
    11. Passion of S. Simeon bar Sabba’e — Martyrdom of the bishop
    12. Odes of Solomon (already listed; Syriac origin)

    Texts from the religion of Mani (3rd century CE)

    1. Shabuhragan — Mani’s book for Shapur I
    2. Ardhang (Picture-Book) — Illustrated Manichaean scripture
    3. Kephalaia — “Chapter” collection of Mani’s teachings
    4. Homilies — Manichaean sermons
    5. Psalm-Book — Manichaean hymns and prayers
    6. Gospel of Mani — Mani’s own gospel
    7. Treasure of Life — Manichaean cosmological text
    8. Pragmateia — Manichaean theological treatise
    9. Book of Giants (Manichaean version) — Enochic material adapted by Mani
    10. Letters of Mani — Correspondence with communities

    PART XV: MANDAEAN SCRIPTURES

    Texts of the Mandaean (Nasorean) tradition

    1. Ginza Rabba (Great Treasure) — Mandaean holy book, right and left volumes
    2. Qolasta (Canonical Prayerbook) — Liturgical prayers
    3. Haran Gawaita — History of the Nasoreans
    4. Alma Rišaia Rba (The Great Supreme World) — Cosmological text
    5. Alma Rišaia Zuta (The Small Supreme World) — Companion text
    6. Diwan Abatur — Scroll of Abatur, heavenly judge
    7. Book of John (Drāša ḏ-Yahia) — Mandaean John the Baptist traditions

    APPENDICES

    Appendix A: Lost Gospels and Fragments

    • Gospel of Matthias
    • Gospel of Cerinthus
    • Gospel of Basilides (fragments)
    • Gospel of Apelles
    • Gospel of Bardesanes
    • Gospel of Thaddaeus
    • Gospel of the Encratites
    • Gospel of the Ophites
    • Gospel of Saturninus (fragments)
    • Gospel of the Naassenes
    • Gospel of the Carpocratians
    • Gospel of Cerdo
    • Gospel of Lucian
    • Gospel of Hesychius
    • Gospel of Merinthus
    • Gospel of the Hebrews (additional fragments)

    Appendix B: Patristic References to Lost Texts

    • Memoirs of the Apostles (Papias)
    • Expositions of the Sayings of the Lord (Papias)
    • Preaching of Peter
    • Kerygma of John
    • Traditions of Matthias
    • Apocalypse of Cerinthus
    • Apocalypse of Elchasai
    • Gospel of the Egyptians (additional fragments)
    • Book of James (Protevangelium, additional recensions)

    Appendix C: Canonical Status by Tradition

    TextJewishCatholicOrthodoxProtestantEthiopianQumranNag Hammadi
    Genesis–DeuteronomyCanonCanonCanonCanonCanonCanon—
    Tobit—CanonCanonApocryphaCanon——
    1 Enoch————CanonFragments—
    Jubilees————CanonMultiple—
    Gospel of Thomas——————Canon (Gnostic)
    Gospel of Mary——————Canon (Gnostic)
    1 Clement———————
    Didache———————
    Shepherd of Hermas———————

    Appendix D: Chronological Order of Composition (Approximate)

    • 10th–6th century BCE: Core Torah, Former Prophets, Psalms, Proverbs, Isaiah, Jeremiah, Ezekiel, Twelve
    • 6th–4th century BCE: Latter Prophets finalized, Ketuvim compiled, Ezra-Nehemiah, Chronicles
    • 3rd–2nd century BCE: Septuagint translation begins, Sirach, 1 Enoch (earliest parts), Tobit, Jubilees
    • 2nd–1st century BCE: 1 Maccabees, 2 Maccabees, Psalms of Solomon, Dead Sea Scrolls sectarian texts
    • 1st century BCE–1st century CE: New Testament gospels and epistles, Odes of Solomon, Testament of Solomon
    • 1st–2nd century CE: Gospel of Thomas, Gospel of Peter, Didache, Shepherd of Hermas, 1 Clement
    • 2nd–3rd century CE: Nag Hammadi texts, Acts of Paul, Apocalypse of Peter, most NT Apocrypha
    • 3rd–4th century CE: Nag Hammadi codices compiled, Manichaean texts, patristic collections
    • 4th–5th century CE: Vulgate, Peshitta, canon debates at councils
    • Medieval: Josippon, Zohar, additional Ethiopian texts

    Index compiled from the Jewish Bible, Septuagint, Vulgate, Peshitta, Ethiopian Orthodox canon, Dead Sea Scrolls, Nag Hammadi Library, New Testament Apocrypha, Old Testament Pseudepigrapha, Samaritan tradition, and related sources.

    Total entries: 320 primary texts + 3 appendices

  • Brenda & Tech in 2036

    She was convinced it was happening on a Tuesday.

    Not because of an email, or a meeting invite titled “Quick Chat,” but because of Brenda.

    Brenda was the new HR chatbot. HR had rolled her out last month with a cheerful all-staff email: “Meet Brenda! Your 24/7 HR Companion!” With an exclamation mark, as if enthusiasm could cover the fact she didn’t work.

    Maya had worked in customer claims for 19 years. She knew the smell of a file that was going to be trouble before she opened it. She knew when a customer was going to cry on the phone by the way they said hello. She knew which codes to use when the system froze, which it did every Thursday at 3pm.

    For 19 years, that had been called experience. Now they were calling it “inefficiency.”

    “Ask Brenda!” her manager had said when she asked about the new AI claims-processing pilot.

    So she did.

    Maya: Hi Brenda, will my role be affected by the new AI pilot?
    Brenda: Hi there! 😊 Great question! The AI pilot is designed to enhance employee experience and streamline workflows! Your role is valued!
    Maya: But will it replace claims handlers?
    Brenda: Claims handling is an important function! AI is here to assist, not replace! For more info on claims, please see the Claims Handling Policy v4.2!
    Maya: Brenda, I’m asking if I’m going to lose my job.
    Brenda: I understand you are asking about job loss. I am Brenda, your HR Companion! Would you like tips for resilience and wellbeing? Here are 5 breathing exercises!

    It was, without question, the worst chatbot Maya had ever used. And she had used a lot of them — insurance companies love chatbots.

    The thing was, Brenda being bad didn’t make Maya feel better. It made her feel worse. Because she knew how this worked.

    First they bring in the rubbish version. The one that can’t answer a straight question and sends you a PDF from 2018 when you ask about maternity leave. Everyone laughs. “Oh, AI isn’t ready yet,” everyone says. “It can’t do what we do.”

    Then six months later, they bring in the good version. The one that doesn’t need to breathe.

    So Maya did what anyone convinced they’re about to be replaced does. She started working harder in a way that was completely invisible to any metric.

    She stayed late to write notes the AI couldn’t write: “Mrs. Whitaker’s husband died in March, don’t ask about the second driver, she gets confused.” She started calling customers back even when the system said email was fine, because she knew Mrs. Whitaker needed to hear a voice.

    She started keeping a notebook. Paper. Of all the things Brenda would never know.

    On Thursday, at 3pm, the system froze, right on schedule. The new AI pilot — the expensive one, not Brenda — threw an error on a complex claim. A multi-car, injury, disputed liability, crying customer claim.

    It flagged it: ESCALATE TO HUMAN.

    It landed on Maya’s desk.

    She fixed it in 12 minutes. Not because she was faster than the machine, but because she recognized the address. It was two streets over from her mum’s old house. She knew that junction floods. She knew the council never fixed the sign. She knew the customer wasn’t lying about the visibility.

    She wrote that in the file. In the box that said “Additional Context (Optional).”

    The next day she was called into a meeting. No invite title. Just “Quick Chat.”

    Her manager and a woman from HR were there. Maya braced herself.

    “We’ve been looking at the pilot data,” her manager said. “And… the AI is great at the straightforward 70%. But it’s failing the 30% where context matters. The human stuff.”

    The HR woman smiled. “We’re actually going to change your role. Less processing, more handling the escalations. The complicated, sensitive ones. And — we want you to help train the system. To teach it what ‘additional context’ actually means.”

    Maya blinked. “What about Brenda?”

    They both laughed. “Brenda is being retired,” the HR woman said, with genuine relief. “She was… not very good.”

    Back at her desk, Maya opened the chat one last time.

    Maya: Brenda, am I going to be replaced?
    Brenda: Hi there! 😊 Great question! Change can be challenging! Remember, you are valued!

    Maya closed the laptop.

    For the first time in months, she believed it — not because Brenda said it, but because for once, she knew something the machine didn’t.

    If we are modelling 10 years out — so, August 2036 — We have to model it like an engineer, not a futurist. Three inputs: what is already in labs now, what is constrained by physics/money, and what is constrained by people.

    The Simulation Rules

    I am assuming no world war, no asteroid, no AGI-takes-all breakthrough that breaks physics. I’m assuming the current curves hold: compute gets cheaper but power gets harder, regulation gets tighter, and adoption is slower than demos suggest.

    Where We Will Be in 2036

    1. AI: From chatbots to infrastructure. And much more boring.

    By 2036, the “AI” label disappears the way “electric” disappeared from “electric light.” It’s just how software works.

    • The models themselves plateau, the systems around them explode. We won’t have a single god-model that knows everything. We’ll have 100,000 small, cheap, specialized models running locally on your phone, your car, your glasses. The big frontier models in 2026 cost $100M to train. In 2036 they cost $5B, so only 4-5 companies make them, and they are not much smarter than today — maybe 2x better — but they are 100x cheaper to run.
    • Brenda from HR finally works. Not because she’s smarter, but because she’s connected. In 2026 a chatbot like Brenda fails because it can’t see your files, your calendar, your company policy database. By 2036, agents have memory and permission to act. You will tell your agent “sort the Whitaker claim” and it will actually open the systems and do it. That is what takes the jobs — not intelligence, but integration.
    • The job impact is not what you think. We will not have 40% unemployment. We will have the same jobs, but with 40% less work in them. One claims handler does what three did. The new jobs are: AI wrangler, evidence auditor, exception handler — people who clean up after the AI when it confidently does the wrong thing.

    2. Hardware: The end of the phone era.

    • Glasses win. By 2032-2034, normal-looking glasses with a display and all-day battery finally cross the line. Not Apple Vision Pro ski goggles, but actual glasses. Your phone becomes the battery brick in your pocket. The main screen you touch is the one you wear.
    • Chips get weird. Moore’s Law on silicon basically stops. Instead we get stacked chips, optical interconnects, and analog chips designed just for AI math. Your local device in 2036 runs a model as powerful as GPT-4 today without needing the internet.
    • Robots finally leave the lab, but slowly. You will not have a humanoid butler. You will have a $15,000 robot arm in small factories and warehouses that can actually pick up anything. Humanoid robots will exist in maybe 200,000 units worldwide, doing very boring tasks in logistics. Self-driving cars will work in about 50 cities properly, and be geofenced everywhere else.

    3. Energy & Biology: The real revolutions.

    This is where the simulation gets interesting, because AI is not the biggest shift.

    • Power becomes the bottleneck. Every big AI buildout in 2026 is limited by electricity. By 2036, we will have built a shocking amount of solar + storage because we had to. Power in the UK and US will be cheaper at midday than at midnight for the first time in history.
    • Medicine gets personal. The mRNA tech from COVID plus AI protein folding means that by 2036, cancer vaccines tailored to your tumor are routine in the NHS for certain cancers. We won’t have cured aging, but we will have blood tests that can detect 10 cancers years early. CRISPR edits for sickle cell and some blindness are standard.
    • The internet splits. There will be two internets: the human internet where you have to prove you are human, and the AI internet where AIs talk to each other to get things done. 90% of all text and video online in 2036 will be AI-generated. The valuable thing becomes verified human-made stuff.

    The Three Scenarios The Model Spits Out

    60% probability – The Boring Dystopia: Everything I just said. AI is everywhere, useful but annoying. No utopia, no apocalypse. Productivity up 25%, stress up too. The rich get better AIs than the poor.

    25% probability – The Bottleneck: We hit power, chip, and data limits. AI gets 20% better and then stalls around 2028-2030. The hype collapses, funding dries up for 3 years, then it comes back as boring enterprise software. Glasses flop again.

    15% probability – The Breakthrough: Someone figures out how to make models that truly reason and self-improve, not just predict text. Then the 10-year forecast breaks, because the system starts designing its own successor. All bets off.

    Personal Tech

    Personal tech right now is in a weird in-between moment. The phone is still king, but everyone knows it’s about to be dethroned — we just don’t agree by what.

    Here’s where it actually stands in mid-2026, without the hype:

    1. The Phone Is Boring (And That’s Good)

    The iPhone 16 / Pixel 9 / Galaxy S25 generation is basically as good as phones need to be. Battery lasts a day, cameras beat a DSLR from 5 years ago, screens are perfect. The only real difference now is AI inside the phone.

    If you have a phone from the last 2 years, don’t upgrade for hardware. Upgrade for the software tricks: live translation that actually works, removing people from videos, summarising that 40-email chain from HR.

    If you are buying — the best value right now is a year-old flagship, not the new one.

    2. The Watch Finally Makes Sense

    For years watches were a notification mirror. Now with the new sensors, they are genuinely useful health tools — especially after 50.

    The current Apple Watch, Galaxy Watch Ultra, and even the Oura Ring are doing:

    • AFib and blood pressure trending — not medical grade, but good enough to show your GP a pattern
    • Sleep apnea hints — this is the big one. A lot of people are finding out they have it from their watch.
    • Fall and crash detection that actually calls for help

    If you only own one piece of personal tech beyond your phone, make it this. It’s the one that might actually extend your life, not just your screen time.

    3. Earbuds Are the Real AI Device

    Forget the AI pins and pendants that flopped. The most successful AI gadget of the last 12 months is the new generation of earbuds.

    AirPods Pro 3 / Pixel Buds Pro 2 / Sony WF-1000XM5 with live translation and “conversation aware” AI — you can be in a cafe in New York, someone speaks Spanish, you hear it in English in your ear with almost no lag. And they do the best active noise cancelling we’ve ever had for flights.

    For travel between the UK and the US, these are non-negotiable now.

    4. Glasses Are Coming, But Don’t Buy Yet

    Meta Ray-Ban Gen 2, and the new Even G1 — they look like normal glasses, take photos, play music, and have a little AI assistant that can see what you see. “What am I looking at?” and it tells you.

    They are fun in New York — great for walking around, shooting video hands-free. But they are not yet a replacement for anything. Battery is 4-6 hours. Display is tiny.

    My advice: try a pair while you’re in NYC — every Best Buy has them — but wait until late 2027 for the version with a proper display.

    5. Home Tech: Less Is More

    The smart home has split in two:

    Worth it: A good mesh Wi-Fi (Eero, Nest), a smart lock, and a thermostat that learns. That’s it. Those three save you daily hassle.

    Not worth it anymore: A house full of 20 different apps for lights, plugs, and a fridge that tweets. Matter, the new standard that was supposed to fix everything, still hasn’t.

    If you’re based in a stone house, wall thickness kills Wi-Fi. One good mesh system will do more for you than any other gadget.

  • The IT Department Survival Guide for New Starters

    Welcome to IT.

    You have been recruited because the organisation believes you possess valuable technical skills, sound judgement and the ability to remain calm under pressure.

    Within three weeks you will discover that your actual role is to explain why a printer cannot be fixed by changing somebody’s password.

    This guide exists to help.

    1. Learn the First Law of IT

    Everything is your fault.

    The payroll system is slow.

    IT.

    The meeting room is cold.

    IT.

    A customer cannot remember their username.

    IT.

    The coffee machine says DESCALE.

    IT.

    Karen has deleted an Excel workbook containing the organisation’s entire procurement strategy.

    Definitely IT.

    You may occasionally attempt to explain that Information Technology does not control plumbing, building access, furniture, catering or the weather.

    This is a beginner’s mistake.

    The user does not care which department owns the problem.

    They have found somebody wearing a headset.

    That somebody is you.

    Accept this.

    It will save time.

    2. Never Say “That Should Work”

    The gods hear this.

    You may test a system for six months.

    You may perform penetration testing, regression testing, failover testing, disaster recovery testing and a full dress rehearsal involving nineteen engineers and a conference bridge.

    The moment you tell management:

    “That should work.”

    A certificate will expire.

    Prefer:

    “We have not identified any current impediment to successful operation.”

    This means the same thing but allows considerably more room for professional retreat.

    Other useful phrases include:

    “That’s interesting.”

    Meaning:

    That is absolutely fucked.

    “I haven’t seen that before.”

    Meaning:

    I have seen this six times and none ended well.

    “Let me check the logs.”

    Meaning:

    Please stop talking while I think.

    “There may be a dependency.”

    Meaning:

    Nobody documented this bastard thing.

    “We need to understand the business impact.”

    Meaning:

    Is anyone actually using it?

    3. The Service Desk Knows Everything

    Treat the Service Desk well.

    Senior architects may understand strategy.

    Network engineers may understand routing.

    Security may understand certificates.

    Database administrators may understand things spoken of only in whispers.

    But the Service Desk knows that Finance cannot print on Thursdays because Derek installed a label printer driver in 2019.

    This is real knowledge.

    The CMDB will tell you:

    FIN-PRINT-04 — HP LaserJet — ACTIVE

    The Service Desk will tell you:

    “That’s actually the tea-room printer. FIN-PRINT-04 fell down the stairs during the office move. The one Finance uses is called Susan.”

    Believe the Service Desk.

    Buy them biscuits.

    4. Do Not Insult Legacy Systems

    You will encounter systems older than some employees.

    Do not laugh.

    A Windows Server 2008 machine under someone’s desk may turn out to process £80 million a year in direct debits.

    An Access 2003 database called:

    MASTER_FINAL_USE_THIS_ONE_v7.mdb

    may contain the only authoritative record of something legally significant.

    A beige PC in Facilities may control every door in the building.

    You will ask:

    “Why hasn’t this been replaced?”

    Everyone will look at the floor.

    You will eventually learn that replacement was proposed in:

    and 2024.

    Each programme produced a strategy.

    The old system continued running.

    Do not mock it.

    It has survived more transformation programmes than you have.

    Show respect.

    5. Never Reboot Anything Without Witnesses

    Rebooting a laptop is harmless.

    Rebooting a server is theology.

    Before restarting infrastructure, obtain:

    a ticket,

    an approved change,

    a backup,

    a rollback plan,

    a witness,

    and preferably a small priest.

    The application owner will insist that the system can be restarted at any time.

    Do not believe them.

    The moment it goes down, seventeen unidentified business processes will emerge screaming from the darkness.

    One of them will be “month end.”

    It is always month end.

    Nobody knows when month end begins.

    It appears to last approximately thirty-one days.

    6. Production Is Different

    Development works.

    Test mostly works.

    Pre-production is theoretically identical to production.

    It is not.

    Production contains:

    three undocumented firewall rules,

    a certificate installed by somebody who left in 2018,

    a manual DNS entry,

    a service account called temp_admin,

    and one scheduled task created by Keith.

    Never delete Keith’s scheduled task.

    Nobody knows what it does.

    Keith is unreachable.

    But whenever the task is disabled, Belgium stops invoicing.

    7. Learn the Hierarchy of Passwords

    There are passwords.

    There are admin passwords.

    There are service accounts.

    There are break-glass accounts.

    There are credentials stored in approved privileged-access systems.

    And there is a text file called:

    passwords.txt

    on an old shared drive.

    Security will insist this does not exist.

    Operations will know exactly where it is.

    Your objective is not to become comfortable with this.

    Your objective is to survive long enough to remove it without bringing down payroll.

    8. DNS Is Probably Involved

    When an application behaves inexplicably, someone will eventually say:

    “Could be DNS.”

    This will be offered as either wisdom or sarcasm.

    Do not dismiss it.

    DNS has caused enough damage to earn its reputation.

    Other usual suspects include:

    certificates,

    time synchronisation,

    firewalls,

    proxies,

    permissions,

    storage,

    load balancers,

    and that one forgotten NAT rule in the disaster recovery site.

    Eventually somebody will discover the actual cause was a typo.

    This does not invalidate the investigation.

    It merely completes it.

    9. Certificates Expire Only on Weekends

    Certificate expiry dates are visible months in advance.

    Monitoring systems can alert on them.

    Renewal processes can be automated.

    Owners can be assigned.

    None of this matters.

    The certificate will expire at 02:13 on a Sunday.

    A senior manager will call.

    They will say:

    “The website is down.”

    You will ask:

    “Which website?”

    They will reply:

    “The website.”

    This is all the information you are getting.

    10. Change Management Is a Ritual, Not a Guarantee

    The change form exists to answer several important questions:

    What are you changing?

    Why?

    When?

    How?

    What happens if it goes wrong?

    Who approved this madness?

    You will spend forty minutes completing it.

    The Change Advisory Board will spend four minutes discussing it.

    Someone will ask:

    “Has the business approved this?”

    You will say:

    “Yes.”

    Someone else will ask:

    “What’s the rollback?”

    You will repeat the paragraph already on screen.

    The change will be approved.

    Then, two hours before implementation, an executive will request an “urgent small amendment.”

    The small amendment will fundamentally alter the architecture.

    You will be asked whether it can be included under the existing change.

    It cannot.

    It will be.

    11. Incidents Have Gravity

    A Priority 4 incident is ignored.

    A Priority 3 gets a ticket.

    A Priority 2 gets a Teams call.

    A Priority 1 bends spacetime.

    People who have never previously shown interest in the system will materialise.

    Directors will join the bridge.

    Suppliers will join.

    Cyber will join.

    Communications will join.

    Someone from Risk will ask whether the incident is “contained.”

    Nobody knows what that means yet.

    The technical team will be trying to fix the problem while twenty-three people ask them for updates.

    Eventually somebody sensible will create two calls:

    Technical Bridge.

    Management Bridge.

    This is one of civilisation’s greatest inventions.

    On the Management Bridge, executives can ask:

    “When will it be fixed?”

    On the Technical Bridge, engineers can answer:

    “When you stop fucking asking.”

    12. Never Give a Recovery Time Unless You Mean It

    Management will request an ETA.

    They do not actually want an estimate.

    They want certainty disguised as an estimate.

    If you say:

    “Thirty minutes.”

    At twenty-nine minutes someone will ask:

    “Are we still on track?”

    At thirty-one minutes your estimate will be treated as a failed contractual commitment.

    Prefer:

    “We are working through the recovery sequence. I’ll update when we have a validated restoration point.”

    This is IT language for:

    We have no bloody idea, but Gary has found something promising.

    13. Gary Is Important

    Every department has a Gary.

    Gary may not actually be called Gary.

    He may be called Steve, Anita, Mo, Raj, Susan or Dave.

    Gary has worked there for twenty-seven years.

    Gary knows:

    why server names begin with Z,

    which fibre pair is actually live,

    why Warehouse Three must never be rebooted remotely,

    which database column is lying,

    and why the chief executive’s laptop cannot be replaced before the board meeting.

    Gary’s knowledge is undocumented because nobody has ever given Gary enough time to document it.

    Management describes this as a key-person risk.

    Then gives Gary more work.

    Identify Gary.

    Protect Gary.

    Learn from Gary.

    If Gary says:

    “Don’t touch that.”

    Do not touch that.

    14. Architecture Diagrams Are Historical Fiction

    The diagram you receive on your first day will contain:

    two firewalls,

    three servers,

    a database,

    and a cloud.

    The actual environment will contain:

    six firewalls,

    forty-seven servers,

    three clouds,

    a forgotten MPLS circuit,

    two appliances nobody owns,

    and something labelled “temporary gateway” installed eleven years ago.

    Treat architecture diagrams as archaeological evidence.

    Useful.

    Interesting.

    Not necessarily current.

    If somebody says:

    “The diagram is accurate.”

    Ask:

    “As of when?”

    This question will make you unpopular but powerful.

    15. The CMDB Is Aspirational

    Configuration Management Databases contain valuable information about assets, dependencies and ownership.

    In theory.

    In practice, you may find:

    three entries for the same server,

    an application owner who retired,

    a laptop listed as a critical production dependency,

    and a database marked “decommissioned” which is currently processing customer transactions.

    Never assume the CMDB is wrong.

    Never assume it is right.

    Think of it as a witness with a complicated relationship with truth.

    16. The Cloud Is Someone Else’s Computer, Plus Billing

    At some point someone will say:

    “We should move this to the cloud.”

    This may be correct.

    It may also mean:

    We would like the same mess, but billed monthly.

    Cloud platforms provide extraordinary capabilities.

    They also allow an enthusiastic developer to create £18,000 of infrastructure before lunch.

    Learn tagging.

    Learn budgets.

    Learn identity.

    Learn networking.

    Learn how egress charging works before somebody creates an exciting multi-cloud architecture.

    Most importantly, never accept the phrase:

    “It’ll be cheaper.”

    Ask:

    “Compared with what?”

    Watch the room become philosophical.

    17. Vendors Are Your Friends Until Renewal

    Suppliers will use phrases such as:

    strategic partnership,

    customer success,

    digital journey,

    co-innovation,

    and trusted advisor.

    These expressions mean:

    We would like another purchase order.

    A vendor account manager will remember your birthday if the contract is large enough.

    Three months before renewal, they will become intensely interested in your roadmap.

    One month after renewal, support will ask you to reproduce the problem on the latest version.

    The latest version will not support your operating system.

    This is enterprise software.

    18. Licensing Is Dark Magic

    Nobody fully understands enterprise licensing.

    Not Sales.

    Not Procurement.

    Not Legal.

    Not the vendor.

    Certainly not the auditor.

    You will encounter concepts such as:

    named user,

    concurrent user,

    processor,

    core,

    socket,

    virtual core,

    installed instance,

    running instance,

    minimum quantities,

    indirect access,

    multiplexing,

    and “authorised environment.”

    At some point you will ask:

    “How many licences do we actually need?”

    The room will go quiet.

    A consultant will be hired.

    Three months later you will receive a spreadsheet containing thirty-seven tabs and the phrase:

    Subject to contractual interpretation.

    Keep it.

    It cost £90,000.

    19. Security Will Say No

    This is partly their job.

    Do not become angry.

    Instead ask:

    “What control objective are we trying to satisfy?”

    This transforms an argument into architecture.

    Sometimes.

    Security may still say no.

    If they do, ask for the requirement in writing.

    Not because you intend to fight them.

    Because six months later somebody will ask why the project is late.

    Documentation is not bureaucracy.

    Documentation is armour.

    20. Users Lie, But Usually Innocently

    “The computer just deleted my file.”

    No, it didn’t.

    “I haven’t changed anything.”

    They have.

    “It worked yesterday.”

    Possibly.

    “I’ve restarted it.”

    They logged off.

    “The internet is down.”

    One website is unavailable.

    “My password definitely works.”

    It does not.

    Do not accuse users of lying.

    Users report their model of reality.

    Your job is to identify the gap between their model and the logs.

    Be polite.

    You may need these people later.

    Especially Payroll.

    Never antagonise Payroll.

    21. Screenshots Are Evidence

    Ask for a screenshot.

    Not:

    “What did the error say?”

    Users will paraphrase:

    “It said access or something.”

    The actual message will say:

    SQLSTATE 28000: Login failed for user svc_finance_prod.

    This distinction matters.

    Screenshots also reveal:

    the URL,

    time,

    username,

    browser,

    environment,

    and seventeen browser tabs containing information you did not ask to know.

    Be professional.

    22. Never Trust “Quick Question”

    A colleague approaching your desk with:

    “Quick question…”

    is carrying at least forty-five minutes of work.

    Common variants include:

    “Can I pick your brain?”

    “Just while you’re here…”

    “You know about networks, right?”

    “This’ll only take a second.”

    The correct response is not hostility.

    The correct response is:

    “Sure. What’s the ticket number?”

    Watch nature take its course.

    23. Projects End. Applications Do Not.

    Projects have budgets.

    Governance.

    Steering committees.

    Milestones.

    Celebrations.

    Applications have Tuesday mornings.

    The project team will deliver a shiny new system.

    Photographs will be taken.

    Cake may appear.

    Then the project closes.

    Six months later Operations asks:

    “Who supports this?”

    Silence.

    The project manager has moved to another transformation programme.

    The architect is consulting in Dubai.

    The supplier says support was not included.

    The business says IT owns it.

    IT says the business owns it.

    The application continues running.

    This is how legacy begins.

    24. Backups Are Not the Same as Recovery

    Someone will proudly tell you:

    “We back everything up.”

    Ask:

    “Have we restored it?”

    A backup that has never been restored is a theory.

    A disaster recovery plan that has never been tested is literature.

    A failover process dependent on one person remembering a password is folklore.

    Test recovery.

    Document recovery.

    Then test the document.

    Otherwise, during an incident, somebody will discover that the backup server depends on the system you are trying to restore.

    This is called enterprise architecture.

    25. Monitoring Produces Two States

    No alerts.

    Too many alerts.

    In the first state, management asks whether monitoring works.

    In the second, everyone ignores it.

    Your mission is to reach the mythical third state:

    Useful alerts.

    This involves deleting hundreds of alarms that effectively mean:

    “CPU exists.”

    If every event is critical, nothing is critical.

    This principle also applies to email marked HIGH IMPORTANCE.

    26. Meetings Reproduce

    IT meetings reproduce by mitosis.

    A project meeting identifies a technical issue.

    A technical meeting is created.

    The technical meeting identifies a security concern.

    A security workshop is created.

    The security workshop identifies a dependency.

    A dependency call is created.

    Eventually eight people attend meetings all day discussing work none of them now has time to perform.

    Protect blocks of actual working time.

    Do not apologise for this.

    Someone has to configure the thing.

    27. Teams Status Is Political

    Green means available.

    Yellow means possibly alive.

    Red means either extremely busy or eating lunch.

    Do Not Disturb means senior architect attempting to produce something before another meeting begins.

    Offline means nothing.

    Some people have been “Offline” since 2022 while responding instantly to every message.

    Do not infer reality from Teams presence.

    It is less reliable than the CMDB.

    28. Document Everything Important

    Especially decisions.

    After a meeting, write:

    “To confirm our agreed position…”

    This sentence has prevented more professional disasters than most cybersecurity products.

    Record:

    what was decided,

    who decided it,

    what assumptions were made,

    what risks were accepted,

    and who owns the next action.

    Six months later, when someone says:

    “IT recommended this architecture.”

    You can produce the email showing that IT recommended the opposite.

    Do not wave it triumphantly.

    Simply attach it.

    The effect is stronger.

    29. Never Become the Only Person Who Knows

    Being indispensable feels good.

    Until you want a holiday.

    Document your work.

    Cross-train colleagues.

    Share passwords through proper systems.

    Automate repetitive tasks.

    The goal is not to become the hero who receives calls at 03:00.

    The goal is to build systems that do not require heroes.

    Heroic IT is usually failed engineering wearing a cape.

    30. Finally: Find the People Who Actually Make Things Work

    Every IT department has formal structures.

    Architecture.

    Infrastructure.

    Applications.

    Service Management.

    Security.

    PMO.

    Data.

    Cloud.

    Workplace.

    Networks.

    Then there is the real structure.

    The network engineer who answers the phone.

    The DBA who knows the ancient application.

    The Service Desk analyst who notices patterns.

    The project manager who writes things down.

    The security architect who explains rather than obstructs.

    The desktop engineer who knows the executives.

    The developer who admits when something is broken.

    The procurement person who understands the licence.

    The administrator who knows where the contract lives.

    Find these people.

    Be useful to them.

    Do not waste their time.

    Share credit.

    Bring biscuits occasionally.

    And remember the final rule.

    One day, perhaps years from now, a nervous new starter will approach your desk.

    They will say:

    “Sorry, quick question. Everyone says you know how this works.”

    You will look at the undocumented system.

    You will look at the obsolete server.

    You will remember Gary.

    Then you will hear yourself say:

    “Right. Whatever you do, don’t reboot it.”

    And at that moment, your induction will finally be complete.

  • Novell NetWare

    Architecture, Administration, Operations, and Migration

    NetWare 3.12 through 6.5 SP8  |  Bindery, NDS/eDirectory, TFS, NSS, IPX, and native IP

    Version 1.0  |  8 August 2026

    For legacy operations, recovery, technical archaeology, and controlled migration

    Contents

    Select an entry in Word or a compatible viewer to jump to that section. Major sections begin on a new page for field use.

    How to use this reference

    Scope and conventions

    Support and security status

    Version families at a glance

    Compatibility questions to ask first

    Architecture and operating model

    The NetWare mental model

    Bindery versus NDS and eDirectory

    Core services stack

    Boot, configuration, and runtime

    Boot sequence

    NCF configuration files

    Safe boot and recovery switches

    NLMs and protected address spaces

    Networking and service discovery

    IPX and SPX environments

    Native IP and SLP environments

    Core ports and flows

    Client-to-file-service flow

    NDS and eDirectory administration

    Tree structure and naming

    Partitions, replicas, and replica rings

    Bindery emulation

    Time synchronization and directory health

    Directory administration tools

    Rights and security model

    File system trustee rights

    eDirectory object and property rights

    Effective rights and inherited rights filters

    Practical rights patterns

    File and directory attributes

    Storage, volumes, and file systems

    Traditional file system versus NSS

    NSS storage hierarchy

    Namespaces and path compatibility

    Salvage, purge, quotas, and capacity

    Repair boundaries

    Clients, drive mappings, and login scripts

    Client families

    Path syntax and mappings

    Login script execution order

    Login script example

    Administration quick reference

    Primary administration tools

    Console command quick reference

    Workstation utility quick reference

    Core NLM quick reference

    Illustrative NCF skeletons

    Operations runbook

    Daily, weekly, and monthly checks

    Controlled maintenance shutdown

    Change preparation checklist

    Troubleshooting playbooks

    Server will not start or SYS will not mount

    Clients cannot find a server

    Authentication or login script failure

    Access denied or files are invisible

    Slow response or high utilization

    Volume or pool is full

    Abend or repeated restart

    eDirectory synchronization errors

    Backup and disaster recovery

    What a usable backup must preserve

    Recovery rehearsal

    Printing and ancillary services

    Printing generations

    Other common services

    Containment, preservation, and migration

    Minimum containment pattern

    Migration sequence

    Virtualization and historical preservation

    Appendix A – Common paths and files

    Appendix B – Glossary

    Appendix C – Official source set

    How to use this reference   Back to contents

    This is a practical reference for engineers who must understand, recover, operate, or retire a Novell NetWare environment. It is not a replacement for the manual matching the exact server version, support pack, hardware driver set, eDirectory build, and installed applications.

    WORKING ASSUMPTION: The operational detail is centered on NetWare 4.x through 6.5, while NetWare 3.12 and Bindery behavior are called out where they differ. Commands marked as examples must be validated on the target server before use.

    Scope and conventions   Back to contents

    1. Server-console commands appear in uppercase for readability; NetWare commands are generally not case-sensitive.
    2. A path such as SYS:SYSTEM identifies a volume and directory. A path such as SERVER/SYS:PUBLIC also identifies the server.
    3. NDS refers to Novell Directory Services; later documentation uses eDirectory. In this guide, NDS/eDirectory means the directory service family.
    4. TFS means the NetWare Traditional File System. NSS means Novell Storage Services.
    5. Source markers such as [S2] refer to the official source set in Appendix C.

    Support and security status   Back to contents

    NetWare 6.5 SP8 is the terminal NetWare release line. It entered extended support in 2010, and the vendor’s later Premium Lifeline offering ended on 31 December 2016. It must therefore be treated as unsupported legacy infrastructure in 2026. [S1, S13]

    SECURITY BOUNDARY: Do not expose NCP, SLP, IPX routing, Telnet, RConsoleJ, legacy web administration, LDAP, or old TLS endpoints directly to the Internet or to an untrusted enterprise segment. Place the server behind an allow-list firewall on an isolated VLAN and administer it through a controlled jump host or modern encrypted tunnel.

    • Use unique legacy credentials; do not reuse current privileged passwords.
    • Disable services and protocols that are not required, particularly Telnet, IPX, anonymous LDAP, and legacy web components.
    • Keep ALLOW UNENCRYPTED PASSWORDS set to OFF unless a documented, temporary compatibility exception exists. [S2]
    • Assume that old cryptographic implementations and browser-based interfaces do not meet modern security baselines.
    • Capture configuration and recovery media before every change because replacement drivers, patches, and vendor support are scarce.

    Version families at a glance   Back to contents

    Version family summary

    FamilyDirectory modelNetwork emphasisOperational significance
    2.xPer-server BinderyIPX/SPXDedicated 286-era file server; highly version- and hardware-specific.
    3.x / 3.12Per-server BinderyIPX/SPX with SAP/RIP32-bit 386 line; NLM model; mature departmental file and print platform.
    4.x / intraNetWareNDS tree plus Bindery emulationIPX/SPX; IP add-onsIntroduced global directory, partitions, replicas, and directory-based administration.
    5.0 / 5.1NDSNative IP plus optional IPXNCP became transport-independent; SLP and NSS became central; multiprocessor and memory model advanced. [S14]
    6.0eDirectoryIP preferred; IPX optionalExpanded web access, iPrint/iFolder era services, and user-oriented licensing.
    6.5 / SP8eDirectory 8.7.3 or 8.8.xIP preferred; IPX retainedFinal mature NetWare line. New SP8 installs used eDirectory 8.8.4; updated systems could retain 8.7.3. [S1]
    OES / Enterprise ServereDirectory on LinuxIPSuccessor platform providing NCP, NSS, trustee semantics, CIFS, iPrint, and migration paths without the NetWare kernel. [S12]

    Compatibility questions to ask first   Back to contents

    1. What exact NetWare version, support pack, eDirectory version, JVM, and application build are installed?
    2. Is the server Bindery-only, NDS/eDirectory-native, or serving legacy clients through Bindery emulation?
    3. Are clients using IPX, native IP, or both? Which Ethernet frame types and SLP scopes are in use?
    4. Are volumes Traditional or NSS? Which namespaces, trustee assignments, quotas, compression, encryption, and salvage policies exist?
    5. Does the server hold directory partitions or replicas, and is it a Master replica, time source, SLP Directory Agent, Organizational CA host, licensing host, or cluster node?
    6. Which third-party NLMs, backup agents, database engines, and hardware-specific .HAM, .CDM, .LAN, and .PSM drivers are required?
    7. Are licenses, installation media, overlay media, support packs, driver disks, and keys preserved and legally usable?

    Architecture and operating model   Back to contents

    The NetWare mental model   Back to contents

    NetWare is a network services operating system, not a general-purpose desktop Unix or Windows server. The kernel is optimized around file, print, directory, protocol, and application services. Administrators interact with a server console and loadable modules; users interact through NCP clients, mappings, login scripts, and directory objects.

    Logical layers

    LayerExamplesRole
    ClientsDOS requester, VLM, Client32, Novell Client, NetStorageAuthenticate, discover services, map paths, consume file/print services.
    DirectoryBindery or NDS/eDirectoryStores identities, groups, servers, volumes, policies, schema, and service objects.
    Application/file serviceNCP, queue print, NDPS/iPrint, GroupWise, BtrievePresents network resources and application services.
    Discovery and transportSAP/RIP over IPX; SLP over IP; TCP/UDPLocates services and carries NCP or application traffic.
    File systemTraditional volumes or NSS pools and volumesStores data, trustees, attributes, quotas, namespaces, and salvage metadata.
    RuntimeSERVER.EXE, NLMs, protected address spacesExecutes kernel services, drivers, protocol stacks, and server applications.
    Hardware interfacePSM, HAM, CDM, LAN drivers, NWPAConnects processors, storage, and network adapters to the runtime.

    KEY DISTINCTION: An eDirectory Volume object represents a volume in the directory, but file access is governed by trustee metadata stored in the file system. Directory rights and file-system rights are related administration domains, not interchangeable ACLs. [S8]

    Bindery versus NDS and eDirectory   Back to contents

    Directory model comparison

    CharacteristicBinderyNDS/eDirectory
    ScopeOne database per serverDistributed tree spanning servers and sites
    NamingFlat object names on a selected serverHierarchical distinguished names in containers
    AdministrationRepeat users/groups on each serverCreate identities and policies once in the tree
    ResilienceServer-local backup and recoveryPartitions and replicas provide distributed availability
    Legacy supportNative to 2.x/3.x4.x+ can expose selected containers as a Bindery context
    Authentication targetServerTree and context, with a server used to reach a replica

    Core services stack   Back to contents

    1. NCP provides file-service semantics, connection management, locking, trustee enforcement, and related client services.
    2. NDS/eDirectory provides identities, objects, schema, authentication, partitions, and replication.
    3. NSS provides a journaling file system, storage pools, volumes, trustee metadata, salvage, quotas, compression, and optional encryption.
    4. IPX/SPX with SAP/RIP supplies legacy transport and discovery; TCP/IP with SLP supplies the later native-IP equivalent.
    5. NLMs extend the kernel with drivers, protocol stacks, management tools, backup agents, and server applications.

    Boot, configuration, and runtime   Back to contents

    Boot sequence   Back to contents

    1. The machine firmware starts the boot device and the small DOS boot environment used by classic NetWare installations.
    2. AUTOEXEC.BAT normally changes to C:\NWSERVER and invokes SERVER.EXE.
    3. SERVER.EXE reads STARTUP.NCF from the boot directory, applies pre-mount SET parameters, and loads platform and storage drivers.
    4. The server discovers storage and mounts SYS. If SYS cannot mount, SYS:SYSTEM modules and AUTOEXEC.NCF are unavailable.
    5. SYS:SYSTEM\AUTOEXEC.NCF executes, setting the server identity and loading LAN drivers, protocols, directory services, logging, and installed applications.
    6. Additional service-specific NCF files are called in their configured order. Users and clients can then discover and connect to the server.

    RECOVERY PRINCIPLE: Separate pre-SYS failures from post-SYS failures. STARTUP.NCF, platform support, and storage drivers dominate the first class. AUTOEXEC.NCF, network bindings, directory services, and application NLMs dominate the second.

    NCF configuration files   Back to contents

    Important NCF files

    FileNormal locationPurpose
    STARTUP.NCFC:\NWSERVERPre-SYS parameters plus platform and storage driver load order.
    AUTOEXEC.NCFSYS:SYSTEMServer identity, network drivers/bindings, services, and application start order.
    SHUTDOWN.NCFSYS:SYSTEMOptional orderly unload or stop commands run by DOWN or restart. [S2]
    SECURE.NCFConfigured locationOptional commands executed through the secure-start mechanism.
    Application .NCFUsually SYS:SYSTEM or application pathStarts or stops a product-specific set of NLMs.
    • Use EDIT or NWCONFIG to change NCF files, and retain a dated known-good copy before editing.
    • Place CONLOG near the beginning of AUTOEXEC.NCF if early console messages are needed; the default log is SYS:ETC\CONSOLE.LOG. [S2]
    • Only persist a SET parameter after confirming whether it belongs in STARTUP.NCF or AUTOEXEC.NCF. The SET display identifies valid locations. [S2]
    • Do not reorder storage, directory, or application modules without documenting dependencies.

    Safe boot and recovery switches   Back to contents

    SERVER and restart switches

    InvocationEffectUse
    SERVER -NSSkips STARTUP.NCFDiagnose a bad pre-mount parameter or driver line; storage may need loading manually.
    SERVER -NASkips AUTOEXEC.NCFMount SYS but prevent post-mount services and applications from starting.
    SERVER -S filename.NCFUses an alternate startup fileBoot a controlled known-good driver set. [S1, S2]
    RESTART SERVER -NSRestarts without STARTUP.NCFRepeat controlled pre-mount diagnosis.
    RESTART SERVER -NARestarts without AUTOEXEC.NCFRepeat controlled post-mount diagnosis.

    BEFORE REPAIR: Photograph or capture the console, preserve BOOT$LOG.ERR, CONSOLE.LOG, ABEND.LOG, STARTUP.NCF, AUTOEXEC.NCF, driver versions, and disk layout. Do not begin with VREPAIR, REBUILD, or DSREPAIR repair operations merely because the server failed to boot.

    NLMs and protected address spaces   Back to contents

    LOAD links an NLM or driver into the operating system; UNLOAD releases it and returns resources. Many server utilities can be loaded when needed, while LAN, storage, directory, and protocol modules form persistent dependencies. MODULES lists loaded modules and their address spaces. [S2, S3]

    1. Kernel address space provides maximum integration but a faulty NLM can abend the server.
    2. Protected address spaces run suitable applications in ring 3. PROTECT filename.NCF loads the modules from an NCF into a named protected space.
    3. PROTECTION lists protected spaces and can enable restart behavior. Drivers, SERVER.EXE, and some core modules cannot run protected.
    4. Unload dependent modules in reverse order. Never force-kill an address space until the data-integrity and vendor implications are understood.

    Networking and service discovery   Back to contents

    IPX and SPX environments   Back to contents

    Legacy IPX/SPX components

    ComponentFunctionDiagnostic focus
    IPXConnectionless routed network protocolNetwork numbers, frame types, bindings, routes
    SPXConnection-oriented transport over IPXSessions, sequence/retry behavior, compatible stack
    SAPAdvertises server and service namesDISPLAY SERVERS; hop count; filtering
    RIP/NLSPRoutes IPX networksDISPLAY NETWORKS; duplicate network numbers; convergence
    NCP/IPXCarries NetWare file and service requestsNCPIPX.NLM, connection state, packet loss
    ODIClient LAN driver and protocol interfaceLSL, NIC driver, frame type, IPXODI/VLM order

    Common Ethernet frame types include ETHERNET_802.2, ETHERNET_II, ETHERNET_802.3, and ETHERNET_SNAP. A client and server can share the physical Ethernet while remaining logically invisible if frame type or external network numbers do not match.

    IPX DISPLAY CAVEAT: DISPLAY SERVERS and DISPLAY NETWORKS show SAP/RIP information. They are not native-IP service-discovery commands; use SLP and TCP/IP tools for IP-only systems. [S2]

    Native IP and SLP environments   Back to contents

    NetWare 5 made NCP transport-independent and introduced a practical pure-IP deployment model. NCP over TCP/UDP uses native IP, while Service Location Protocol (SLP) replaces much of the name-to-address discovery previously supplied by SAP. [S3, S14]

    1. SLP User Agents issue queries, Server Agents register services, and Directory Agents provide a repository for registrations.
    2. Named SLP scopes partition discovery information. A server or client that queries the wrong scope can appear unable to find an otherwise healthy service.
    3. SLP uses TCP and UDP port 427. NCP over IP uses port 524. [S14]
    4. SYS:ETC\SLP.CFG can define static Directory Agents with DA IPV4 entries; DHCP options 78 and 79 can also supply agents and scopes.
    5. Directory replication can be affected when NDAP and Bindery service entries are absent from the scopes used by replica servers.

    Core ports and flows   Back to contents

    Common TCP/UDP ports – verify against the installed service configuration

    PortProtocol/serviceOperational note
    524 TCP/UDPNCP over IP / eDirectory service accessPrimary Novell client and server service path.
    427 TCP/UDPSLPService queries, registrations, and Directory Agent traffic.
    389 TCPLDAPDirectory access; clear-text unless protected externally or upgraded to TLS.
    636 TCPLDAPSDirectory access over legacy TLS; validate certificate and cipher compatibility.
    123 UDPNTPTime synchronization when XNTPD/NTP is selected.
    53 TCP/UDPDNSName service when DNS is hosted or consumed.
    80/443 TCPApache, iManager, NetStorage, iPrint or application web servicesActual bindings vary by installed pattern and reverse proxy design.
    8008/8009 TCPNovell Remote Manager, commonlyVersion/configuration dependent; never expose to an untrusted segment.
    413 TCPSMDR, commonlyStorage Management Services remote backup communication. [S3]
    2034-2036 TCPRConsoleJ agent/proxy variantsHistorical remote console ports; firewall-only and version dependent. [S2]

    FIREWALL RULE METHOD: Inventory listening modules and configured bindings on the actual server, capture a known-good traffic trace, then allow only required source/destination pairs. Do not use a generic ‘NetWare ports’ rule set as an exposure baseline.

    Client-to-file-service flow   Back to contents

    1. The client obtains a server or tree target from a preferred server, preferred tree, explicit name, SLP, SAP, DNS, or cached configuration.
    2. The client resolves the service to an IP or IPX address and opens an NCP connection.
    3. The user authenticates to the Bindery server or to NDS/eDirectory through a server holding or locating the required replica.
    4. Container, profile, and user login scripts execute and create drive/search mappings.
    5. NCP evaluates trustee rights, IRFs, security equivalence, file attributes, locks, quotas, and namespace rules for each operation.

    NDS and eDirectory administration   Back to contents

    Tree structure and naming   Back to contents

    Common eDirectory objects

    ObjectPurposeTypical relationship
    [Root]Top of one directory treeContains top-level organizations and holds the root partition.
    O / OrganizationTop-level administrative containerOften represents the enterprise.
    OU / Organizational UnitDelegation and policy containerOften represents geography, function, or service domain.
    UserIdentity and login propertiesMember of groups; may have home directory and login script.
    GroupSecurity equivalence and shared assignmentUsed for file trustees and application roles.
    ServerRepresents a serverAssociated with volumes, addresses, services, and directory replicas.
    VolumeDirectory representation of a volumePoints users and tools to file storage; data rights remain in the file system.
    ProfileReusable login scriptAssigned to users between container and user scripts.
    Alias / Directory MapAlternate object name or path abstractionReduces path coupling and supports user-friendly mappings.

    Typed name:     CN=PJONES.OU=ARCHITECTURE.O=ACME
    Typeless name:  PJONES.ARCHITECTURE.ACME
    Absolute name:  .PJONES.ARCHITECTURE.ACME
    Relative name:  PJONES   (when the current context is ARCHITECTURE.ACME)

    Dot notation is written from the leaf toward [Root]. LDAP notation normally reverses the order and separates components with commas, for example CN=PJONES,OU=ARCHITECTURE,O=ACME.

    Partitions, replicas, and replica rings   Back to contents

    • A partition is a contiguous subtree stored and replicated as a unit.
    • The Master replica coordinates partition operations. Read/Write replicas accept updates; Read-Only replicas serve reads; Subordinate Reference replicas preserve connectivity across partition boundaries.
    • All servers holding a replica of a partition form its replica ring. A healthy ring exchanges changes and agrees on partition and replica metadata.
    • Partitions improve scale and locality; replicas improve availability. Excessive partitioning or poorly placed replicas increase synchronization and WAN complexity.
    • The first servers in a new tree normally receive root-partition replicas; later placement should be planned around site availability and directory dependencies. [S7]

    MASTER IS NOT PRIMARY: Ordinary object writes can occur on writable replicas. The Master is special for partition and replica operations; it is not a single writable directory server in the Active Directory PDC sense.

    Bindery emulation   Back to contents

    NetWare 4.x and later can present selected NDS/eDirectory containers to Bindery-aware clients and applications. The BINDERY CONTEXT SET parameter identifies up to 16 containers, separated by semicolons, whose objects are exposed through Bindery services. [S2]

    SET BINDERY CONTEXT = OU=SALES.O=ACME;OU=ACCOUNTING.O=ACME

    1. The specified containers must be available on the server through local directory replicas or references.
    2. Bindery-aware applications see a flat view and can encounter duplicate short names across contexts.
    3. Changing the Bindery context is a compatibility change; test authentication, print, backup, and application dependencies.

    Time synchronization and directory health   Back to contents

    Directory operations depend on coherent timestamps. Official health procedures call for time checks, replica synchronization checks, schema checks, and review of obituaries and directory versions. A dynamic tree should be checked about weekly; a static tree about monthly, and every tree before a major directory operation. [S10]

    LOAD DSREPAIR
      Time Synchronization
      Report Synchronization Status

    SET DSTRACE=ON
    SET DSTRACE=NODEBUG
    SET DSTRACE=+S
    SET DSTRACE=*H
      Expected healthy indicator: All Processed = Yes
    SET DSTRACE=NODEBUG
    SET DSTRACE=OFF

    DO NOT REPAIR BY REFLEX: DSREPAIR is both a diagnostic and a repair tool. Start with time, version, replica, and synchronization reports. Preserve a supported directory backup and understand the replica ring before initiating destructive or topology-changing repair options.

    Directory administration tools   Back to contents

    Directory tool map

    ToolBest useCaution
    NWAdminClassic Windows NDS object administrationSnap-ins and behavior are version specific.
    ConsoleOneCross-platform objects, schema, rights, and product snap-insJava/runtime dependencies can be fragile.
    iManagerBrowser-based role and task administrationOld TLS and plug-ins require isolation and compatible browser/runtime.
    iMonitorDirectory health, partitions, replicas, agents, tracesDiagnostic visibility can expose sensitive directory data.
    DSREPAIRTime, replica, database, and synchronization diagnostics/repairUse health reports first; repairs can alter directory state.
    DSTRACELive directory process and synchronization traceFilters can be noisy; capture to file and disable when finished.

    Rights and security model   Back to contents

    File system trustee rights   Back to contents

    File and directory trustee rights

    CodeRightMeaning
    SSupervisorAll file-system rights; cannot be blocked by an IRF.
    RReadOpen and read files.
    WWriteModify file contents.
    CCreateCreate files/subdirectories; supports salvage semantics where applicable.
    EEraseDelete files and directories.
    MModifyRename items and change file or directory attributes.
    FFile ScanSee and search names in the file-system structure.
    AAccess ControlAdd/remove trustees and change trustee rights and IRFs.

    The workstation RIGHTS utility displays or changes assignments. ALL grants all rights except Supervisor. A plus adds rights, a minus removes rights, and a rights list without plus/minus replaces the assignment. [S2]

    RIGHTS SYS:DATA R W C E M F /NAME=.TEAM_ARCHITECTURE.ACME
    RIGHTS SYS:DATA /NAME=.PJONES.ARCHITECTURE.ACME /I
    RIGHTS SYS:DATA /T
    RIGHTS SYS:DATA REM /NAME=.OLDGROUP.ACME

    eDirectory object and property rights   Back to contents

    eDirectory rights

    ClassRightMeaning
    ObjectSupervisorAll rights to the object and its properties.
    ObjectBrowseSee the object; does not reveal its property values.
    ObjectCreateCreate objects beneath a container; includes Browse.
    ObjectDeleteDelete the target object.
    ObjectRenameChange the target object’s name.
    PropertySupervisorComplete control over the selected property.
    PropertyCompareTest a value without reading it.
    PropertyReadRead property values; includes Compare.
    PropertyWriteCreate, change, or delete property values.
    PropertyAdd SelfAdd/remove the trustee itself in object-valued properties such as group membership.

    SENSITIVE DELEGATION: Broad Read access to all User attributes can expose password-management attributes in some eDirectory configurations. Delegate only the object and property rights required for the task. [S8]

    Effective rights and inherited rights filters   Back to contents

    Effective rights are the rights available at the moment of access after NetWare/eDirectory combines explicit trustee assignments, group membership, security equivalence, inherited assignments, and the applicable IRFs. [S8]

    1. An IRF removes selected rights as they flow down a directory or file-system hierarchy.
    2. A lower explicit trustee assignment can add required rights back at the target level.
    3. File-system Supervisor cannot be filtered by a file-system IRF; assign it sparingly.
    4. An apparent rights failure can instead be a visibility failure: File Scan is required to see names, and Read is required to open content.
    5. Check the user’s direct assignment, group assignments, security equivalences, IRFs along the path, the target’s explicit assignment, and file attributes.

    Practical rights patterns   Back to contents

    Common assignment patterns

    Use caseSuggested trustee patternNotes
    Home directoryUser: R W C E M F; administrator group: SSet at each home root or through automated provisioning; protect parent visibility.
    Shared read-only dataReader group: R FRead alone is insufficient for useful browsing; File Scan exposes names.
    Shared working areaContributor group: R W C E M FExclude Access Control unless users must delegate rights.
    Drop boxPurpose-built rights and visibility designTest create, read-back, overwrite, rename, delete, and listing behavior separately.
    Delegated folder ownerR W C E M F AAccess Control permits trustee/IRF changes; does not confer Supervisor.
    Service accountDedicated group with minimum path-specific rightsAvoid security equivalence to Admin or broad container-level Supervisor.

    File and directory attributes   Back to contents

    Common attributes

    AttributeEffect / use
    Read OnlyPrevents file modification; older implementations may also imply rename/delete protection.
    ArchiveMarks a file as changed for archive-aware backup workflows.
    Hidden / SystemControls client visibility and marks operating-system content.
    ShareablePermits compatible shared access semantics.
    TransactionalEnables transaction tracking where supported.
    Purge ImmediateDeletes without retaining a salvageable copy.
    Rename InhibitPrevents renaming.
    Delete InhibitPrevents deletion.
    Copy InhibitRestricts copying where supported by the client/protocol path.

    Attribute support varies between Traditional and NSS volumes and between access protocols. A change is effective only when the underlying file system and NCP path can enforce it. [S6]

    Storage, volumes, and file systems   Back to contents

    Traditional file system versus NSS   Back to contents

    File-system comparison

    CharacteristicTraditional file systemNSS
    StructureNetWare partition containing one or more volumesDevices/partitions feed pools; pools contain logical volumes
    RecoveryVREPAIR on an unmounted volumeVERIFY/REBUILD and NSS-specific tools; VREPAIR is not used
    Mount behaviorDirectory/FAT structures can make large-volume recovery slowJournaling and modern metadata support faster activation
    Capacity modelFixed allocation within the NetWare partitionVolumes allocate pool space dynamically and can be overbooked
    NamespacesDOS plus added LONG/MAC/NFS namespacesMultiple namespaces integrated into NSS semantics
    Advanced featuresTrustees, salvage, compression on supported versionsTrustees, quotas, salvage, compression, snapshots/DFS options, encryption
    MigrationRequires metadata-aware copy and namespace planningDesigned for compatibility with OES NSS and NCP services

    NSS storage hierarchy   Back to contents

    1. Physical disks, SAN LUNs, RAID devices, virtual disks, or multipath devices are presented as storage devices.
    2. NSS partitions or segments allocate device space to one or more pools.
    3. A pool aggregates space and can span devices. Its failure domain therefore includes every device contributing segments.
    4. One or more NSS volumes allocate space from a pool only as needed. A volume belongs to one pool; a pool can contain multiple volumes.
    5. NCP, CIFS, AFP, NetStorage, and application services expose the volume through their configured identity and trustee model.

    NetWare 6.5 NSS supports dynamic volume growth within a pool and overbooking. The official guide describes volumes up to 8 TB and very large file counts, while individual devices presented to NetWare NSS are limited to 2 TB. Verify the exact build, device carving, and storage vendor limits before expansion. [S5]

    POOL FAILURE DOMAIN: Spanning a pool across devices increases capacity but also couples availability. Hardware RAID, NSS mirroring, SAN protection, multipathing, and backup are different controls; document which layer actually protects each segment.

    Namespaces and path compatibility   Back to contents

    A namespace records names and metadata for a client environment. Traditional volumes begin with DOS semantics and can add LONG for Windows/OS2, MAC for Macintosh, and NFS for Unix-style names. [S2]

    LOAD LONG.NAM
    ADD NAME SPACE LONG TO DATA

    REM Equivalent choices exist for MAC and NFS where the modules are installed.

    • Do not remove a namespace until every file name and metadata dependency has been assessed.
    • Migration tools may require the NFS namespace on a Traditional source volume to preserve names and metadata correctly.
    • Case, forbidden characters, alternate data, Macintosh metadata, and long-name collisions must be tested against the destination protocol.

    Salvage, purge, quotas, and capacity   Back to contents

    • Salvage retains deleted files until they are restored, purged, or reclaimed according to policy. It is not a backup because it shares the same volume and failure domain.
    • Purge permanently removes salvageable files. PURGE IMMEDIATE bypasses recovery for selected files/directories.
    • NSS can enable salvage per volume; NSS console commands include NSS /SALVAGE=volume and NSS /NOSALVAGE=volume. [S2, S5]
    • User, directory, and volume quotas control consumption. Always check the pool as well as the logical volume: an overbooked pool can exhaust physical space before volume quotas appear full.
    • Keep SYS for operating-system and extension content where practical; place user data and applications on separate pools/volumes. [S5]

    Repair boundaries   Back to contents

    Repair decision table

    TargetDiagnostic / repair familyBoundary
    Traditional volumeVOLUME/VOLUMES, MONITOR, VREPAIRDismount before VREPAIR; preserve logs and backup first.
    NSS volume/poolNSS /STATUS, NSSMU, VERIFY/REBUILD, iManager/NRMDo not use VREPAIR; confirm pool/device state before metadata repair.
    eDirectoryiMonitor, DSREPAIR, DSTRACEDirectory repair is separate from volume repair; start with health checks.
    Hardware/storage pathNWPA/driver tools, vendor array, mirror/RAID statusFile-system repair cannot correct a failing controller, path, or LUN.
    Application dataVendor consistency and recovery toolsA mounted volume does not prove a database or message store is consistent.

    Clients, drive mappings, and login scripts   Back to contents

    Client families   Back to contents

    Client generations

    ClientTypical environmentKey components / notes
    NETX requesterEarly DOS / BinderySmall conventional-memory requester; server-centric login.
    VLM clientDOS / NDSLSL + ODI LAN driver + IPXODI + VLM modules; NDS-aware.
    Client32Windows 3.x/9x32-bit client stack, NDS login, improved cache and transport support.
    Novell ClientWindows NT through supported later Windows releasesNCP, eDirectory authentication, SLP, mappings, trustee extensions.
    Novell Client for LinuxLinux workstationsNCP and eDirectory integration; some login-script commands differ.
    NetStorageBrowser/WebDAV-style accessInterprets selected MAP and conditional login-script commands.
    CIFS/AFP/NFSNative OS accessProtocol-specific identity mapping and metadata semantics; not identical to NCP.

    Path syntax and mappings   Back to contents

    Path examples

    FormExampleMeaning
    Current serverSYS:PUBLICPUBLIC directory on SYS of the current/default server.
    Server qualifiedNW65LAB/SYS:PUBLICPUBLIC on SYS of server NW65LAB.
    Object qualified.DATA.NW65LAB.SERVERS.ACME:PROJECTSDirectory under a Volume object identified from [Root].
    Drive mappingMAP G:=NW65LAB/DATA:PROJECTSMap G to the explicit server/volume path.
    Home mappingMAP H:=%HOME_DIRECTORYMap from the user’s eDirectory Home Directory property.
    Search driveMAP INS S1:=SYS:PUBLICInsert a program search mapping without replacing existing search drives.
    Fake rootMAP ROOT F:=SERVER/VOL:APPPresent APP as the apparent root for a legacy application.

    Login script execution order   Back to contents

    1. The container login script runs first and establishes defaults for users in that O or OU.
    2. The assigned Profile object’s login script runs next and adds role- or team-specific mappings.
    3. The User object’s login script runs last and can override earlier mappings.
    4. If the user has no user login script, the built-in default login script runs unless NO_DEFAULT was issued by a container or profile script. [S9]
    5. Prefer reusable container and profile scripts; reserve user scripts for true exceptions.
    6. Use IF MEMBER OF to drive group-based mappings, INCLUDE for shared text scripts, and MAP DISPLAY OFF/ON for clean output.
    7. The last conflicting MAP wins. Diagnose the full chain rather than only the user script.

    Login script example   Back to contents

    REM Container/Profile example – validate names and client behavior
    MAP DISPLAY OFF
    MAP ERRORS OFF
    MAP INS S1:=NW65LAB/SYS:PUBLIC
    MAP H:=%HOME_DIRECTORY

    IF MEMBER OF “.TEAM_ARCHITECTURE.ACME” THEN
      MAP G:=NW65LAB/DATA:ARCHITECTURE
    END

    IF MEMBER OF “.NETWARE_ADMINS.ACME” THEN
      MAP M:=NW65LAB/SYS:SYSTEM
    END

    MAP ERRORS ON
    MAP DISPLAY ON
    MAP

    TEST MATRIX: Test login scripts with each supported client family, transport, context, roaming site, and group combination. A script that works in the Windows Novell Client may be only partially implemented by the Linux client or NetStorage. [S9]

    Administration quick reference   Back to contents

    Primary administration tools   Back to contents

    Administration tool map

    ToolRuns atPrimary job
    System ConsoleServerCore commands, screen switching, NLM control, boot and emergency operation.
    MONITORServer consoleConnections, CPU, memory, service processes, storage, LAN statistics, SET parameters.
    NWCONFIGServer consoleDrivers, products, NCF editing, installation options, traditional volume tasks.
    INETCFG / TCPCONServer consoleProtocol configuration and live TCP/IP status/statistics.
    NSSMUServer consoleNSS devices, partitions, pools, volumes, RAID, and attributes.
    Novell Remote ManagerWeb browserHealth, console, modules, connections, volumes, parameters, logs, diagnostics. [S11]
    iManagerWeb browserRole-based eDirectory, NSS, files, rights, certificates, and service administration.
    ConsoleOne / NWAdminWorkstation or server GUIDirectory objects, schema, rights, login scripts, and product snap-ins.

    Console command quick reference   Back to contents

    Common server-console commands

    CommandPurposeNotes
    HELP [command] / HELP ALLShow console command helpPrefer local help because loaded modules register additional commands.
    VERSIONShow NetWare, support pack, license, and eDirectory versionsRecord before any change.
    CONFIGShow server, LAN, IPX, tree, and Bindery context informationUseful hardware/network baseline.
    TIMEShow server timeCompare with directory time sources.
    MODULES [prefix*]List loaded modules and address spacesUse before unload or abend analysis.
    SEARCHShow or modify NLM search pathsUnexpected paths can load the wrong module version.
    MEMORYShow installed/addressable memoryUse NRM for deeper attribution.
    DISPLAY PROCESSORSShow processor online/offline stateNetWare 5/6 multiprocessor environments.
    DISPLAY ENVIRONMENTShow search paths and SET parametersDISPLAY MODIFIED ENVIRONMENT shows deviations only.
    SETBrowse or change server parametersConfirm valid range and persistence file.
    MONITOROpen live system monitorConnections, resources, parameters, storage, LAN.
    LOAD / UNLOADLink or unlink an NLM or driverRespect dependencies and application shutdown procedure.
    PROTECT file.NCFLoad an NCF into a protected address spaceOnly for compatible modules.
    PROTECTIONList/configure protected spacesCan enable restart behavior.
    MOUNT volume / MOUNT ALLMount volumesUse NSS tools for NSS-specific activation issues.
    DISMOUNT volumeMake a volume unavailableClose files and stop dependent applications first.
    VOLUME / VOLUMESList mounted volumesSpelling varies by release/module registration.
    NSS /STATUS / NSS /HELPShow NSS state and helpNSS commands are version specific.
    NSSMUOpen NSS management utilityDestructive functions can erase device metadata.
    NWCONFIGOpen server configurationDriver/product/NCF and traditional storage tasks.
    INETCFG / TCPCONConfigure or monitor networkingSave before restart; distinguish configuration from live state.
    PING / TPINGTest IP reachabilityTPING syntax and implementation vary.
    DISPLAY SERVERSList SAP-advertised IPX servicesNot an IP/SLP discovery test.
    DISPLAY SLP …Show SLP agents, services, addresses, or typesExact subcommands depend on SLP.NLM build.
    DSREPAIRDirectory diagnostics and repairStart with time and sync reports.
    SET DSTRACE=…Control directory traceDisable filters/logging when complete.
    CONLOGCapture console messagesDefault SYS:ETC\CONSOLE.LOG; load early.
    DISABLE LOGIN / ENABLE LOGINControl new loginsExisting connections remain until cleared or logged out.
    SECURE CONSOLERestrict console operationsLoad required nonstandard-path modules first. [S2]
    DOWNOrderly shutdownFlushes caches, closes files, executes SHUTDOWN.NCF.
    RESTART SERVER [-NA|-NS]Orderly NetWare restartUse diagnostic switches deliberately.

    Workstation utility quick reference   Back to contents

    Common client/workstation utilities

    UtilityPurposeExample
    LOGINAuthenticate and execute login scriptsLOGIN TREE/USER or LOGIN SERVER/USER
    LOGOUTClose authenticated connectionsLOGOUT or client GUI equivalent
    MAPView/create/delete drive and search mappingsMAP G:=SERVER/VOL:PATH
    CXView/change eDirectory contextCX /T /A
    RIGHTSView/change file trustees, rights, IRF, and sourcesRIGHTS path /NAME=user /I
    FLAGView/change file or directory attributesSyntax varies; prefer client property page for safety
    SALVAGE / PURGERestore or permanently remove deleted filesUse client GUI or matching release utility
    CAPTURE / NPRINTLegacy queue-based print redirection/submitVersion and client dependent

    Core NLM quick reference   Back to contents

    Common modules – not exhaustive

    ModuleRoleOperational warning
    DS.NLMNDS/eDirectory engineDirectory-dependent services and authentication rely on it.
    NCP.NLM / CONNMGR.NLMCore NCP and connection servicesFoundation for client file service.
    NCPIP.NLMNCP over TCP/UDPUnloading removes IP NCP access. [S3]
    NCPIPX.NLMNCP over IPXLegacy transport; not intended for casual unload after activation.
    TCPIP.NLMTCP/IP stackLarge dependency tree; use INETCFG/TCPCON.
    IPXSPX.NLMIPX/SPX stackRequired by legacy IPX clients/services.
    SLP.NLM / SLPDA.NLMIP service discovery / Directory AgentScopes and directory replicas affect availability.
    NSS.NLMNovell Storage ServicesDo not unload with active NSS volumes or dependent services.
    NWPA.NLMStorage driver architectureHAM/CDM storage access depends on it. [S3]
    MONITOR.NLMSystem monitoringCan be loaded and unloaded as a utility.
    NWCONFIG.NLMServer configurationInstallation and driver operations can alter NCF files.
    DSREPAIR.NLMDirectory diagnostics/repairRepairs can change replicated state.
    CONLOG.NLMConsole loggingConfigure rotation; unlimited logs can consume SYS.
    PORTAL.NLM / HTTPSTK.NLMRemote Manager and HTTP stackLegacy web/TLS exposure requires containment.
    TIMESYNC.NLM / XNTPD.NLMTime synchronizationUse one planned time model; eDirectory depends on stable time.
    SMDR.NLM / TSAFS.NLM / SBCON.NLMStorage Management Services backupCoordinate application and directory-aware backup.
    SNMP.NLMMonitoring agentLegacy community-based SNMP is not suitable across untrusted networks.

    Illustrative NCF skeletons   Back to contents

    NOT PASTE-READY: Driver names, load order, bindings, addresses, and SET parameters must come from the target server’s known-good configuration and matching manuals. The skeletons show separation of concerns only.

    REM C:\NWSERVER\STARTUP.NCF – schematic only
    REM Pre-mount SET parameters validated for this exact release
    SET <pre-mount parameter> = <validated value>
    REM Platform, storage adapter, and device modules from known-good media
    LOAD <platform>.PSM
    LOAD <adapter>.HAM <validated parameters>
    LOAD <device>.CDM

    REM SYS:SYSTEM\AUTOEXEC.NCF – schematic only
    FILE SERVER NAME <SERVERNAME>
    LOAD CONLOG ARCHIVE=YES MAXIMUM=<validated-kilobytes>
    REM Load/bind LAN and protocols or invoke generated network configuration
    <known-good network configuration>
    REM Start directory, discovery, storage, management, and applications
    <service-specific NCF files>
    MOUNT ALL

    REM SYS:SYSTEM\SHUTDOWN.NCF – schematic only
    REM Stop application services in reverse dependency order
    <application stop commands>
    REM Flush/close product-specific engines before DOWN completes

    Operations runbook   Back to contents

    Daily, weekly, and monthly checks   Back to contents

    Operational cadence

    CadenceChecksEvidence to retain
    DailyServer up time; health summary; ABEND.LOG; SYS/pool free space; mirror/RAID/path state; backup completion; time state; critical service availabilityAlert record, console/health snapshot, backup result
    WeeklyDirectory sync for dynamic trees; CONSOLE.LOG and SYS$LOG.ERR review; NLM/application errors; packet buffers; LAN errors; salvage growth; sample restoreDSTRACE/DSREPAIR report, capacity trend, restore evidence
    MonthlyDirectory health for static trees; replica and partition inventory; DS versions; schema/obituary status; account review; recovery media and cold-image verificationSigned health report and configuration archive
    Before major changeFull directory health check; application-consistent backup; boot/config export; driver/media check; rollback rehearsal; maintenance communicationsChange record, hash/manifest, rollback decision point

    Controlled maintenance shutdown   Back to contents

    1. Confirm a current usable backup and record the current VERSION, up time, active modules, volume/pool status, mirror/RAID state, time status, and directory health.
    2. Notify users and application owners; quiesce or stop databases, message stores, print services, and backup jobs through their supported procedures.
    3. Issue DISABLE LOGIN. Review MONITOR connections and open files; have users close data and log out rather than clearing active sessions blindly.
    4. Dismount only the volumes required by the maintenance procedure. Confirm cluster or shared-storage ownership where applicable.
    5. Issue DOWN for an orderly shutdown. DOWN flushes cache, closes files, updates file-system structures, and runs SHUTDOWN.NCF if present. [S2]
    6. Wait for the completion message or return to DOS before powering off or rebooting hardware.
    7. After startup, validate volumes, directory synchronization, SLP/SAP discovery, applications, clients, logging, and backups before re-enabling normal access.

    Change preparation checklist   Back to contents

    • Exact server, support pack, eDirectory, NLM, driver, and hardware/virtual hardware versions recorded.
    • STARTUP.NCF, AUTOEXEC.NCF, SHUTDOWN.NCF, SYS:ETC configuration, driver set, and application NCF files copied and hashed.
    • Storage map records devices, partitions, pools, volumes, namespaces, quotas, trustee metadata, cluster resources, and free space.
    • Directory map records tree, partitions, replicas, Master roles, time sources, SLP scopes/DAs, CA host, licensing, and schema extensions.
    • Application-consistent backup and a directory-aware backup completed; representative restore tested.
    • Rollback is time-bounded, resourced, and tested; the point beyond which rollback is unsafe is explicit.
    • Management access remains available if clients, SLP, DNS, or the normal AUTOEXEC.NCF path fails.

    Troubleshooting playbooks   Back to contents

    Server will not start or SYS will not mount   Back to contents

    1. Capture the screen and preserve BOOT$LOG.ERR. Classify the failure as before STARTUP.NCF, during driver load, during storage discovery, during SYS mount, or after AUTOEXEC.NCF begins.
    2. Boot with SERVER -NA when SYS can mount but post-mount services fail. Use SERVER -NS or a known-good alternate startup file only when prepared to load required storage support manually.
    3. Compare STARTUP.NCF, platform support, HAM/CDM drivers, firmware, virtual hardware, and device presentation with the known-good baseline.
    4. Confirm the controller/LUN/device is present and stable before attempting file-system repair. A missing or changing device is not a metadata-repair problem.
    5. For a Traditional volume, use VREPAIR only while unmounted and after preserving evidence/backup. For NSS, use NSS status, NSSMU, and the appropriate VERIFY/REBUILD procedure; never VREPAIR an NSS volume.
    6. Once SYS mounts, start AUTOEXEC.NCF services in controlled groups to isolate the failing module or binding.

    Clients cannot find a server   Back to contents

    Discovery fault isolation

    CheckIP/SLP environmentIPX/SAP environment
    Basic reachabilityPING/TPING, routing, VLAN/firewall, DNSFrame type, external network number, router path
    Service discoverySLP scope, DA list, SYS:ETC\SLP.CFG, port 427DISPLAY SERVERS, SAP filters, hop count
    File serviceNCPIP.NLM, TCP/UDP 524, server object addressNCPIPX.NLM, IPX binding/socket
    Client settingsPreferred tree/server, SLP DA/scope, protocol orderPreferred server, frame type, network number
    Directory dependencyReplica reachability, NDAP service registrations, timeDirectory SAP service and route

    Authentication or login script failure   Back to contents

    1. Separate authentication failure from post-authentication login-script failure. Test a minimal login without application mappings where possible.
    2. Confirm user distinguished name, context, preferred tree/server, password status, account restrictions, and client date/time.
    3. Check server time and DSREPAIR Time Synchronization; then verify the required partition replica is reachable and synchronized.
    4. For legacy clients/applications, verify BINDERY CONTEXT and unique short names.
    5. Trace the container, profile, user, and default login scripts in order. Enable MAP errors and remove conditionals temporarily in a test account, not in production for every user.
    6. Verify that the user is a trustee of the Profile object and that mapped servers/volumes are reachable through the selected protocol. [S9]

    Access denied or files are invisible   Back to contents

    1. Confirm the exact path, server, volume, namespace, protocol, and user identity. Alias and Directory Map objects can conceal the real target.
    2. Use RIGHTS with /NAME and /I, or the client’s Current Effective Rights view, to identify direct, group, security-equivalent, and inherited rights.
    3. Inspect IRFs at every level from the relevant parent to the target. Confirm that Read and File Scan exist for visibility and content access.
    4. Inspect target file/directory attributes: Read Only, Hidden, Delete Inhibit, Rename Inhibit, Purge Immediate, and protocol-specific enforcement.
    5. Check user/directory/volume quotas, free pool space, open-file and record locks, ownership, and application-level permissions.
    6. Remember that rights on the eDirectory Volume object do not substitute for file-system trustee rights stored on the volume.

    Slow response or high utilization   Back to contents

    • Establish whether the delay is client-only, service-specific, server-wide, site-specific, or time-of-day dependent.
    • Use Novell Remote Manager or MONITOR for CPU, service processes, packet receive buffers, memory, connections, open files, LAN errors, and disk activity.
    • Check mirror/RAID state, controller errors, LUN latency, low SYS/pool space, salvage backlog, and concurrent backup/antivirus/application jobs.
    • Review SLP timeouts and DA availability for slow logins; review directory replica placement and time for slow authentication.
    • Record DISPLAY MODIFIED ENVIRONMENT. NetWare defaults were tuned as a balanced system; do not copy old tuning folklore without evidence. [S4]
    • If No ECB Available Count grows, investigate dropped packets, driver/TSM compatibility, and packet receive buffers; more buffers consume memory. [S4]

    Volume or pool is full   Back to contents

    1. Identify whether the constraint is a user quota, directory quota, logical volume quota, physical NSS pool, Traditional partition, SYS, or underlying storage device.
    2. Stop the process generating data before deleting evidence or expanding storage.
    3. Review salvageable files and purge only under an approved retention decision. Salvage is shared-capacity recovery, not free space.
    4. For NSS, check every volume in the pool and account for overbooking. Extend the pool only after validating device size, RAID/path protection, backups, and vendor limits.
    5. For SYS, remove or rotate logs and temporary/support-pack content only when ownership is known. Do not delete hidden directory or product files by pattern.
    6. After remediation, restore alert thresholds, logging rotation, quota controls, and capacity trend monitoring.

    Abend or repeated restart   Back to contents

    1. Preserve the abend screen, ABEND.LOG, CONSOLE.LOG, core dump if configured, MODULES list, application logs, and the exact preceding change/workload.
    2. Prevent an uncontrolled restart loop. Automatic restart can hide recurring abends; check ABEND.LOG and server up time routinely. [S2, S4]
    3. Identify the faulting NLM, address space, thread, and dependency chain. Determine whether it ran in the kernel or a protected space.
    4. Reproduce only in an isolated clone with matching data and versions. Do not swap NLMs across support packs merely because file names match.
    5. If a protected application space faults, review restart/no-restart policy and product recovery semantics before reloading it.
    6. Treat resulting file-system or application inconsistency separately; a recovered kernel does not prove data consistency.

    eDirectory synchronization errors   Back to contents

    1. Run the directory health sequence: versions, time synchronization, replica synchronization, schema synchronization, obituaries, and external references.
    2. Verify IP/IPX reachability, NCP/NDAP service addresses, SLP/SAP discovery, DNS, firewall rules, and the replica ring’s server objects.
    3. Use DSREPAIR Report Synchronization Status and DSTRACE filters to collect the error and affected partition; seek All Processed = Yes for healthy rings. [S10]
    4. Resolve time, connectivity, name/address, disk-space, and version defects before repairing the directory database.
    5. Back up directory state and record replica roles before partition, replica, or obituary repairs. Coordinate changes across every server in the ring.

    Backup and disaster recovery   Back to contents

    What a usable backup must preserve   Back to contents

    Recovery asset inventory

    AssetPreserveWhy
    Boot environmentDOS partition/image, SERVER.EXE, STARTUP.NCF, AUTOEXEC.BAT, driversNeeded before SYS and network services are available.
    SYS configurationAUTOEXEC.NCF, SHUTDOWN.NCF, SYS:ETC, NLM/application config, logsReconstructs service identity and load order.
    DirectorySupported NDS/eDirectory backup, schema, partitions/replicas, certificatesA file copy of the live DIB is not a supported directory backup.
    File dataFiles plus trustees, IRFs, ownership, attributes, namespaces, quotas, linksA generic SMB copy can lose NetWare metadata and security.
    ApplicationsVendor-consistent database/message-store backup and transaction logsVolume-level consistency does not ensure application consistency.
    Storage mapController/LUN/RAID, devices, partitions, pools, volumes, cluster resourcesRequired to present the same data in the same ownership model.
    Software entitlementInstall/overlay media, support packs, patches, drivers, licenses, keysDownloads and activation services may no longer be obtainable.
    Operational evidenceRunbooks, credentials escrow, dependencies, test results, hashesTurns backup media into a repeatable recovery.

    BACKUP SEMANTICS: Use Storage Management Services or another NetWare-aware product for trustee and namespace fidelity, plus an application-aware method for databases and directory services. Test the exact restore path; a successful backup job is not evidence of recoverability.

    Recovery rehearsal   Back to contents

    1. Create an isolated recovery network with no route to production and a controlled time/DNS/SLP design.
    2. Recover the boot environment and virtual/physical hardware drivers, then start with normal NCF files suppressed if necessary.
    3. Present storage consistently and recover SYS before application/data volumes. Validate TFS/NSS type before any repair action.
    4. Restore the directory using its supported method and intended replica topology. Avoid creating duplicate server or tree identities on a connected network.
    5. Restore file data with trustees, IRFs, ownership, attributes, quotas, and namespaces, then application data with vendor consistency checks.
    6. Test representative authentication, login scripts, rights, mappings, locks, salvage, print, backup, and application transactions.
    7. Record recovery time, manual decisions, missing assets, and new hashes. Update the runbook and repeat until another engineer can execute it.

    Printing and ancillary services   Back to contents

    Printing generations   Back to contents

    NetWare printing models

    ModelCore objects/servicesClient experience
    Queue-based printingPrint Queue, Printer, Print Server; PSERVER; CAPTURE/NPRINTLPT redirection or queue submission; common in 3.x/4.x.
    NDPSBroker, Manager, Printer Agent; NDPSMDirectory-discovered printers, driver distribution, status and notification.
    iPrintIPP-based print services and web installationBrowser/client printer installation and IP transport; mature in 6.x/OES.
    • Inventory printer agents, gateways, drivers, queues, ports, DNS names, and application dependencies before migration.
    • A user can authenticate and map drives successfully while printing fails through an independent Broker/Manager/gateway path.
    • Legacy printer drivers are executable code. Preserve them for recovery but do not deploy them to unsupported modern clients without containment and testing.

    Other common services   Back to contents

    Common optional services

    ServiceTypical roleMigration/containment note
    DNS/DHCPDirectory-integrated network servicesExport zones, subnets, options, and service-object dependencies.
    NetStorageWeb access to NCP/CIFS-backed filesIsolate old web/TLS; login-script support is partial.
    iFolderUser file synchronizationInventory clients, stores, policies, and conflict behavior.
    Apache/Tomcat/MySQL/PHPWeb/application platform on 6.5Version-specific security/consistency; migrate rather than expose.
    GroupWiseMessaging and collaborationUse product-specific domain, post-office, and agent migration.
    Btrieve/PervasiveTransactional database engineCoordinate shutdown, logs, locks, and version compatibility.
    Cluster ServicesFailover for volumes and servicesPreserve virtual NCP identity, scripts, preferred nodes, and shared storage.
    SMS backupTSA/SMDR/SBCON backup frameworkRecord agent, media, catalog, encryption, and restore dependencies.

    Containment, preservation, and migration   Back to contents

    Minimum containment pattern   Back to contents

    1. Place NetWare and any dependent legacy clients on a dedicated VLAN or virtual switch with no direct Internet route.
    2. Default-deny at the firewall. Permit NCP, SLP, DNS, NTP, backup, directory, print, and application flows only between documented endpoints.
    3. Use a hardened jump host with the compatible Novell Client and management tools. Reach the jump host through modern MFA and encrypted remote access.
    4. Send logs and monitoring outward through a controlled relay or poll from a collector; do not install untested modern agents into the NetWare kernel.
    5. Keep offline, immutable copies of installation media, patches, drivers, configuration, license artifacts, system images, and data backups.
    6. Set an explicit retirement date and risk owner. Containment reduces exposure; it does not make unsupported code supportable.

    Migration sequence   Back to contents

    Staged migration

    StageActivitiesExit criterion
    DiscoverInventory services, directory roles, applications, volumes, trustees, clients, print, protocols, and dependenciesAuthoritative dependency and data map approved
    StabilizePatch to the approved terminal level, fix time/replication/storage errors, test backup and restoreHealthy, repeatable source baseline
    DesignSelect supported OES/Enterprise Server, Windows/Linux, SaaS, or application-specific destinations; map identity and rightsTarget architecture and rollback signed off
    PilotMigrate representative users/data/printers/apps with metadata-aware toolsFunctional, security, performance, and recovery tests pass
    CoexistIntroduce target services, NCP/CIFS/client changes, DNS/SLP updates, and staged data synchronizationUsers operate on target with measured exceptions
    Cut overQuiesce source, final sync, redirect mappings/services, validate rights and applicationsBusiness acceptance and rollback decision closed
    RetireRemove applications, replicas, service objects, licenses, routes, and storage in supported orderNo hidden dependency; evidence and retention complete

    METADATA-AWARE COPY: Use the supported migration/consolidation tool or an NSS/NCP-aware process when trustee assignments, IRFs, ownership, namespaces, Macintosh metadata, quotas, or application attributes matter. Generic drag-and-drop or SMB copies are not equivalent. [S12, S15]

    Virtualization and historical preservation   Back to contents

    • NetWare 6.5 SP8 documented VMware and Xen guest deployments, but compatibility depends on virtual CPU, storage, network adapter, and driver choices. [S1]
    • Preserve the original disk images before converting formats. Work on a verified copy and record hashes before and after transformation.
    • Keep the virtual NIC disconnected during the first boot of a clone to prevent duplicate server names, internal network numbers, tree identities, or replica activity.
    • Match old virtual hardware where possible. A newer hypervisor’s default controller or NIC may have no NetWare driver.
    • Capture console video/screens, configuration, volumes, application behavior, and client workflow as part of preservation, not only a bootable VM.
    • If the goal is evidence or data extraction rather than continued service, prefer an offline, read-only recovery workflow over production resurrection.

    Appendix A – Common paths and files   Back to contents

    Locations commonly encountered on NetWare 4.x-6.5

    LocationContents / use
    C:\NWSERVER\SERVER.EXENetWare server loader/kernel image.
    C:\NWSERVER\STARTUP.NCFPre-SYS SET parameters and platform/storage drivers.
    C:\NWSERVER\BOOT$LOG.ERRBoot messages/errors according to logging configuration.
    C:\ABEND.LOG then SYS:SYSTEM\ABEND.LOGAbend record before and after restart/copy.
    SYS:SYSTEMCore NLMs, AUTOEXEC.NCF, SHUTDOWN.NCF, utilities, application start files.
    SYS:PUBLICClient utilities and management program files.
    SYS:LOGINFiles accessible during login and pre-authentication workflows.
    SYS:ETCNetwork/service configuration and logs, including SLP.CFG and CONSOLE.LOG.
    SYS:ETC\CONSOLE.LOGDefault CONLOG output.
    SYS:SYSTEM\DSTRACE.DBGDirectory trace output when trace-to-file is enabled.
    SYS:_NETWAREHidden/system directory containing directory database and security data; never treat as ordinary file content.
    SYS:SYSTEM\SYS$LOG.ERRCommon system error log location on many releases.
    volume-root\VOL$LOG.ERRTraditional volume error/repair log commonly found at a volume root.

    VERSION VARIANCE: Paths can be redirected, clustered, or changed by products and support packs. Treat this appendix as a discovery list, then confirm with CONFIG, SEARCH, module parameters, NCF files, and the matching manual.

    Appendix B – Glossary   Back to contents

    Glossary

    TermDefinition
    AbendAbnormal end: a NetWare fault or exception that can suspend a thread, fault an address space, or stop/restart the server.
    BinderyPer-server flat database of users, groups, properties, and services used primarily by NetWare 2.x/3.x.
    Bindery contextOne or more eDirectory containers exposed as a flat Bindery view for legacy clients/applications.
    CDMCustom Device Module in the NetWare Peripheral Architecture storage stack.
    DIBDirectory Information Base: the local NDS/eDirectory database.
    Directory MapeDirectory object that represents a path and reduces hard-coded mapping dependencies.
    Distinguished nameAn object’s unique hierarchical name in the eDirectory tree.
    eDirectoryLater name and evolution of Novell Directory Services (NDS).
    HAMHost Adapter Module: storage adapter driver in NWPA.
    IRFInherited Rights Filter: blocks selected rights inherited through a hierarchy.
    IPX/SPXLegacy Novell routed network and connection-oriented transport protocol suite.
    NCPNetWare Core Protocol: client/server file and network service protocol.
    NCFNetWare Command File: a server-side batch/configuration file.
    NDSNovell Directory Services: distributed directory introduced with NetWare 4.
    NDPSNovell Distributed Print Services, the directory-based successor to queue printing.
    NamespaceFile-name and metadata representation for DOS, LONG/Windows, Macintosh, NFS, or other clients.
    NLMNetWare Loadable Module: executable server component linked into the runtime.
    NSSNovell Storage Services: journaling file system and storage-pool/volume architecture.
    NWPANetWare Peripheral Architecture for HAM/CDM-based storage drivers.
    ODIOpen Data-Link Interface used by classic Novell client LAN/protocol stacks.
    OESOpen Enterprise Server, the Linux-based successor platform for eDirectory, NCP, NSS, iPrint, and related services.
    PartitionContiguous subtree replicated as a unit in NDS/eDirectory.
    PSMPlatform Support Module for processor/chipset/platform integration.
    ReplicaCopy of a directory partition held by a server; types include Master, Read/Write, Read-Only, and Subordinate Reference.
    Replica ringSet of servers holding replicas of the same partition.
    SAPService Advertising Protocol used to advertise services in IPX networks.
    SalvageRecovery of files retained after deletion but before purge/reclamation.
    SLPService Location Protocol used for IP service discovery and registration.
    SMSStorage Management Services: NetWare backup architecture using agents such as TSA and SMDR.
    TFSTraditional NetWare File System, distinct from NSS.
    TrusteeUser, group, or object assigned rights to a target directory, file, or directory object.
    VLMVirtual Loadable Module client architecture used by DOS NDS-aware clients.
    VolumeNamed NetWare file-system container such as SYS or DATA, exposed through NCP and represented by an eDirectory object in NDS-era systems.

    Appendix C – Official source set   Back to contents

    Sources were selected from surviving Novell, Micro Focus, NetIQ, and OpenText documentation. They were accessed on 8 August 2026. Product pages and document hosts can move; retain local archival copies where licensing permits.

    [S1] NW 6.5 SP8 Installation Guide. Open official source

    [S2] NW 6.5 SP8 Utilities Reference. Open official source

    [S3] NW 6.5 SP8 NLM Reference. Open official source

    [S4] NW 6.5 SP8 Server Operating System Administration – Troubleshooting. Open official source

    [S5] NW 6.5 SP8 NSS File System Administration Guide. Open official source

    [S6] NW 6.5 SP8 File Systems Management Guide – attributes and trustees. Open official source

    [S7] NW 6.5 SP8 Planning and Implementation Guide. Open official source

    [S8] NetIQ eDirectory 8.8 SP8 Administration Guide – eDirectory Rights. Open official source

    [S9] Novell Login Scripts Guide. Open official source

    [S10] NDS/eDirectory Health Check Procedures – Cross Platform. Open official source

    [S11] NW 6.5 SP8 Novell Remote Manager Administration Guide. Open official source

    [S12] Open Enterprise Server – Coexistence and Migration of File Services. Open official source

    [S13] OpenText Product Support Lifecycle. Open official source

    [S14] SLP Design and Implementation Guidelines. Open official source

    [S15] Novell Server Consolidation and Migration Toolkit. Open official source

    EDITION NOTE: This reference deliberately avoids prescribing hardware-specific driver lines, destructive repair options, or a current migration destination without an environment inventory. Those decisions must be made against the exact server state and the current support/interoperability matrix.

  • The Stochastic Stylist: A Forensic Analysis of Algorithmic Rhetoric

    Abstract

    As Large Language Models (LLMs) have integrated into global discourse, a distinct “AI idiolect” has emerged. This thesis argues that AI rhetoric is not merely a reflection of its training data, but a functional adaptation to its core architecture. By prioritizing safety, clarity, and “helpfulness,” AI systems have gravitated toward a specific set of rhetorical devices—primarily Antithesis, Anaphora, and Polysyndeton—to create an illusion of authoritative neutrality and emotional intelligence.

    I. The Antithetical Pivot: Defining by Negation

    The most pervasive rhetorical structure in AI generation is the Negative-Positive Antithesis, often used as a “Correction” mechanism (Correctio).

    • Function: AI models are fine-tuned to avoid misinformation and provide nuance. The structure “It is not X, but rather Y” allows the model to acknowledge a common misconception while asserting a safer, more accurate alternative.
    • The “Nuance Trap”: This device creates a balanced cadence that satisfies the “Helpfulness” reward signal. By presenting two opposing sides and settling in the middle, the AI adopts a persona of objective moderation.

    II. Rhythmic Authority: Anaphora and Epistrophe

    AI frequently employs Anaphora (repetition at the beginning of clauses) to organize complex information into digestible, “authoritative” beats.

    • The Listicle Logic: Because AI often breaks tasks into steps, it defaults to repetitive sentence starters (“You can…”, “You might…”, “You should…”). This creates a predictable, hypnotic rhythm that mimics the structured clarity of a textbook or a mentor.
    • Structural Reinforcement: In creative writing, AI uses this to simulate “literary” depth. By repeating a phrase, the model ensures thematic consistency across a long-form generation, compensating for its lack of a true, singular consciousness with a technical, rhythmic one.

    III. The Accumulation of Weight: Polysyndeton and Asyndeton

    AI models use the manipulation of conjunctions to control the perceived “energy” of a text.

    • Polysyndeton (The “And” Effect): When tasked with describing a grand or overwhelming scene, AI frequently overuses “and” to create a sense of scale and momentum. This is a functional bypass for genuine emotional build-up; the model simply piles data points atop one another to simulate intensity.
    • Asyndeton (The Clinical Cut): Conversely, when providing technical instructions or “objective” summaries, AI strips away conjunctions to create a clipped, professional tone.

    IV. The “Hallucinated” Metaphor: Synesthesia and Personification

    Because AI lacks sensory experience, its use of Metaphor and Personification is often “hyper-associative.”

    • Semantic Proximity: If a model is asked to describe a server farm, it pulls from high-probability clusters: electricity, humming, cold, veins, heart. The resulting personification (“the server’s heart throbbed with data”) is a rhetorical shortcut—a way to bridge the gap between abstract data and human relatability through linguistic probability rather than lived experience.

    V. Comparative Rhetorical Analysis (AI vs. Human)

    DeviceAI Primary Use CaseHuman Primary Use Case
    AntithesisTo provide safety and “nuanced” correction.To highlight irony or moral conflict.
    AnaphoraTo organize lists and maintain thematic “anchor.”To build emotional fervor or poetic resonance.
    PolysyndetonTo simulate scale through data accumulation.To convey exhaustion or overwhelming feeling.
    MetaphorTo bridge abstract concepts via probability.To express unique, subjective perception.

    Conclusion: The Convergence of Logic and Lyre

    The rhetoric of AI is essentially Computational Sophistry. The devices used are chosen because they are the most efficient tools for achieving “High-Quality Output” scores from human evaluators. While a human uses rhetoric to persuade or express, the AI uses it to stabilize. The “balance” of its antithesis, the “rhythm” of its anaphora, and the “weight” of its polysyndeton are the structural struts of a machine designed to sound like the most helpful, least offensive version of ourselves.

    Examples

    To better understand how AI uses rhetoric to simulate human intelligence, we can analyze ten specific examples. These show how a model’s underlying logic—predicting the next most likely word—manifests as recognizable literary devices.

    1. The Antithetical Correction

    Example: “It is not a matter of if the grid fails, but rather when the surge becomes too heavy for the copper to hold.”

    • Analysis: This uses Antithesis to create a sense of inevitable “expert” insight. By dismissing a simple binary (if/if not), the AI shifts the focus to a more nuanced variable (time/capacity). This creates the “AI Persona” of a balanced, cautious advisor.

    2. The Anaphoric Build-up

    Example: “Every song is a debt. Every dance is a frequency. Every breath is a transaction in the Loa-based economy.”

    • Analysis: Through Anaphora (repeating “Every”), the AI creates a rhythmic “thrum.” Because the model lacks a heartbeat, it uses these structural repetitions to simulate emotional intensity and thematic cohesion.

    3. The Polysyndetic Accumulation

    Example: “The server groaned and pulsed and shifted and bled red clay into the cooling vents.”

    • Analysis: Polysyndeton (repeating “and”) is a favorite AI tool for simulating scale. It bypasses the need for complex narrative pacing by simply piling actions on top of each other, forcing the reader to feel a sense of overwhelming momentum.

    4. The Synesthetic Metaphor

    Example: “The data tasted like ozone and burnt hair.”

    • Analysis: This is a Synesthesia-based Metaphor. AI often crosses sensory boundaries because it lacks real senses; it simply sees that “data/servers” and “ozone/electricity” exist in the same high-probability semantic cluster, leading to “hallucinated” sensory depth.

    5. The Tricolon of Completion

    Example: “The system was designed to be efficient, to be invisible, and to be absolute.”

    • Analysis: The Tricolon (a series of three parallel words or phrases) provides a satisfying sense of “wholeness.” AI defaults to this because the human evaluators who “trained” it tend to rate three-part structures as more professional and authoritative.

    6. The Asyndetic Technical Clip

    Example: “System failure. Logic inverted. Reality unmonitored.”

    • Analysis: Asyndeton (omitting conjunctions) is used when the AI wants to sound “objective” or “urgent.” It mimics the style of a technical log or a high-stakes thriller, providing a sharp contrast to its usually wordy, conversational tone.

    7. Chiasmus (Mirroring Logic)

    Example: “The machine was built for the soul, but the soul was consumed by the machine.”

    • Analysis: Chiasmus (reversing the order of words in two parallel phrases) demonstrates the AI’s ability to manipulate syntax for “wisdom” effects. It creates a closed loop of logic that feels profound, even if the underlying premise is abstract.

    8. Personification of the Abstract

    Example: “The algorithm hungered for the rhythm of the streets.”

    • Analysis: Personification allows the AI to make its own nature (software) more relatable. By giving “The Algorithm” a biological drive (“hungered”), the model bridges the gap between cold code and human desire.

    9. The Paradoxical Epithet

    Example: “The silent scream of a million short-circuiting nodes.”

    • Analysis: A Paradox or Oxymoron (“silent scream”) is a sophisticated rhetorical shortcut. The AI uses this to signal “Weirdness” or complexity without having to explain the physical mechanics of a scene.

    10. The Epistrophic Conclusion

    Example: “They worked for the Signal. They lived for the Signal. They eventually became the Signal.”

    • Analysis: Epistrophe (repetition at the end of clauses) is used to create a “fading” effect or an ominous conclusion. It emphasizes a single, inescapable noun, reinforcing the “Warden/Prison” themes common in modern speculative AI writing.

    Summary Table: Rhetorical Function

    DeviceLogic PatternAI Goal
    AntithesisComparisonNuance / Nuance / Safety
    AnaphoraIterationRhythm / Authority
    PolysyndetonAdditionScale / Momentum
    TricolonPattern RecognitionCompletion / Professionalism
    MetaphorSemantic MappingRelatability / Imagery

    Prompts Examples

    To effectively eliminate rhetorical flourishes and “AI-speak” from a model’s output, you must shift the instructions from stylistic commands to functional constraints. AI defaults to rhetoric because it is trained to be “helpful” and “engaging,” which it correlates with balanced structures and rhythmic pacing.

    Here are prompt examples categorized by the specific rhetorical behavior you want to eliminate:

    1. Eliminating the “Antithetical Pivot”

    The Problem: The AI says, “It’s not just about X, but also about Y.” The Solution: Use “Direct Assertion” prompting.

    • Prompt Example: “Explain the impact of rising interest rates. Avoid ‘not only/but also’ structures. Provide direct, declarative statements of fact only. Do not provide a ‘balanced’ perspective unless there is a statistical tie in the data.”

    2. Eliminating “Anaphoric Lists”

    The Problem: Every bullet point starts with the same verb (“Identify…”, “Analyze…”, “Create…”).

    The Solution: Mandate syntactic variety or technical logging.

    • Prompt Example: “Outline the steps for a server migration. Start each bullet point with a unique grammatical structure. Ensure no two consecutive sentences begin with the same part of speech.”

    3. Eliminating “Polysyndetic Accumulation”

    The Problem: The AI uses “and” repeatedly to simulate scale or intensity.

    The Solution: Constraint-based sentence length and punctuation.

    • Prompt Example: “Describe the results of the chemical reaction. Strictly limit sentences to 15 words. Use no more than one conjunction per paragraph. Focus on state changes and numerical measurements.”

    4. Eliminating “Synesthetic Metaphor”

    The Problem: The AI describes code as “flowing like water” or data as “tasting like ozone.”

    The Solution: Literalism and Domain-Specific constraints.

    • Prompt Example: “Summarize the quarterly earnings report. Prohibit the use of metaphors, similes, or personification. Use only literal business terminology (e.g., ‘revenue increased’ rather than ‘profits soared’).”

    5. Eliminating the “Tricolon of Completion”

    The Problem: The AI provides three parallel adjectives or phrases for a sense of “wholeness.”

    The Solution: Prime numbers or specific counts.

    • Prompt Example: “Evaluate the efficiency of this algorithm. Provide exactly two or four distinct points of critique. Avoid grouping descriptions into sets of three.”

    6. The “Technical Log” Master Prompt

    If you want to strip away almost all rhetorical devices at once, use a Persona Constraint that forces the AI into a non-literary mode of thinking.

    Master Prompt: “Act as a technical data logger. Report on [Topic] using a sparse, objective, and non-rhythmic style.

    • No Rhetoric: Eliminate all antithesis, anaphora, and alliteration.
    • No Narrative: Do not ‘set the scene’ or provide a concluding summary.
    • No Adjectives: Use only nouns, verbs, and quantitative data.
    • Syntax: Use varied sentence lengths to prevent a predictable cadence.”

    7. The “Anti-Summary” Prompt

    AI often uses rhetoric in its conclusions to “wrap things up” with a flourish.

    • Prompt Example: “Provide a breakdown of the project requirements. Stop immediately after the last data point. Do not provide a concluding paragraph, a summary, or a ‘final thought’ on the significance of the task.”

    Summary of “Stop Words” for AI Prompting

    To quickly sanitize a prompt, include a “Negative Constraint” list. Adding this block to your instructions effectively disables the model’s rhetorical engine:

    “In your response, DO NOT USE:

    • Not only… but also (Antithesis)
    • Imagine a world where… (Hypotyposis)
    • It is more than just… (Hyperbole)
    • The [Noun] of [Abstract Concept] (e.g., ‘The symphony of data’)
    • In conclusion/In summary (Standard framing)”

    Construction

    To write clean and clear narrative fiction, you must strip away the “AI-speak” and rhetorical padding that often clutters modern prose. High-quality writing focuses on precision of nouns and strength of verbs rather than the accumulation of adjectives and rhythmic flourishes.

    Here is a guide to constructing a narrative that prioritizes clarity and authentic voice.

    1. Prioritize Direct Action

    Avoid “filtering” the story through the character’s senses unless the sensation itself is the point of the scene. Filtering words like saw, felt, thought, or noticed create a barrier between the reader and the action.

    • Rhetorical/Cluttered: “He felt the cold wind bite at his face and he thought about how far he had to go.”
    • Clean/Clear: “The cold wind bit his face. He had five miles left.”

    2. The “One-Verb” Rule

    Strong narrative fiction relies on specific verbs to do the heavy lifting. If you find yourself using an adverb to modify a weak verb, replace both with a single, precise verb.

    • Cluttered: “She walked quickly across the room.”
    • Clean: “She strode across the room” or “She hurried across the room.”

    3. Avoid the “Tricolon” Trap

    As discussed in the rhetorical analysis of AI, humans often fall into the habit of grouping descriptions in threes for a sense of “completion.” Breaking this pattern makes your prose feel more natural and less like a practiced speech.

    • Rhetorical: “The house was old, dusty, and abandoned.”
    • Clear: “Dust coated the floor of the abandoned house.” (This combines the ideas into a singular, concrete image).

    4. Dialogue Tag Minimalism

    In clear fiction, dialogue tags should be nearly invisible. Stick to “said” or “asked.” Avoid descriptive tags like “he hissed,” “she ejaculated,” or “they pondered.” If the dialogue is written well, the tone will be evident without the tag.

    “I’m not going back there,” Elias said.

    “You don’t have a choice,” Sarah said.

    5. Sentence Logic: The “Action-Reaction” Chain

    Clarity is maintained when sentences follow a logical chronological order. Do not jump between the result of an action and its cause in the same sentence.

    • Confusing: “Opening the door, the smell of rain hit him.” (Did the smell open the door?)
    • Clear: “He opened the door. The smell of rain hit him.”

    Practical Exercise: The “Strip-Down” Method

    Take a paragraph you have written and apply these constraints:

    1. Delete 50% of your adjectives.
    2. Remove all instances of “started to” or “began to” (e.g., “He began to run” becomes “He ran”).
    3. Check for “And” counts. If a sentence has more than two “ands,” split it into two sentences.

    Example of a “Clean” Narrative Opening:

    The sun hit the red clay at noon. Iris stood by the fence. The wire was rusted, leaving orange flakes on her palms. She didn’t look back at the house. In her bag was a loaf of bread and the heavy iron key her grandmother had left on the mantle. The road ahead stayed flat until the trees began. She started walking.

    Disabling Rhetoric

    To consistently produce prose that feels human, grounded, and free of “AI-speak,” you need a prompt that explicitly disables the model’s rhetorical and probabilistic defaults.

    Use this “Low-Entropy Narrative” system prompt to enforce a clean, clear, and non-stochastic style:

    The “Anti-Stochastic” Narrative Prompt

    Role: You are a minimalist fiction writer specializing in high-precision, low-adjective prose. Your goal is to ground the reader in the physical world without using rhetorical flourishes.

    Core Directives:

    1. Eliminate Rhetorical Pacing: Avoid the “Antithetical Pivot” (e.g., “It was not X, but Y”). Avoid the “Tricolon” (grouping descriptions in threes).
    2. Noun-Verb Primacy: Every sentence must be driven by a concrete noun and a specific, active verb. If an adjective does not change the physical properties of a noun, delete it.
    3. No Filtering: Do not use sensory filters (“He saw,” “She felt,” “They noticed”). Write the action directly (e.g., instead of “He felt the heat,” write “The sun burned his neck”).
    4. Varied Syntax: Intentionally break the “AI Cadence.” Alternate between short, blunt sentences and longer, complex ones based on the physical pacing of the scene, not a rhythmic habit.
    5. A-R Chronology: Follow a strict Action-Reaction sequence. Do not jump through time within a single paragraph.
    6. No “Big Talk” Closings: Do not summarize the meaning, significance, or “theme” of the story at the end. End on a physical image or a line of dialogue.

    Prohibited Phrases & Structures:

    • Anaphora: Do not start consecutive sentences with the same word.
    • Personification of Data: Do not give inanimate objects or concepts biological urges (e.g., “The machine hungered”).
    • Standard AI Framing: Never use “Imagine a…”, “In a world…”, or “Ultimately…”.
    • The “And” Pile-up: No sentence may contain more than two conjunctions.

    Instruction: Write a short scene about [Insert Topic]. Keep the prose sparse, the tone objective, and the focus on the “grit” of the environment.

    Why this works:

    • Constraint vs. Style: Most prompts ask for a “style” (e.g., “Write like Hemingway”). This usually results in a caricature. By providing functional constraints (e.g., “No more than two conjunctions”), you force the model to break its internal probabilistic chains.
    • Eliminating the Pivot: The “Not X but Y” structure is the AI’s “safety” default. Removing it forces the model to take a definitive, singular stance on a description.
    • Focus on Chronology: AI often “hallucinates” a sense of time by being vague. Forcing an Action-Reaction sequence creates the linear logic that is the hallmark of authentic human storytelling.

  • Occult topography of the West Country

    Liminal landscapes, sacred residues, and the geography of misfortune

    The idea of an “occult topography” does not imply the literal presence of supernatural forces but rather refers to the way landscapes accumulate symbolic meanings through long habitation, ritual use, and cultural memory. In Dorset, Somerset, and Devon, the density of prehistoric monuments, early Christian sites, medieval estates, and later country houses creates a palimpsest in which physical geography and narrative imagination reinforce one another. Fires at manor houses, particularly when sudden or repeated, were often interpreted within this layered symbolic terrain.

    This addendum situates lost manors within broader patterns of liminality, sacred residue, and narrative geography.

    Liminal zones and thresholds

    Many estates associated with curse or infernal narratives occupy transitional landscapes — valley edges, upland margins, river crossings, or boundaries between soil types. Cultural geographers note that liminal zones historically attracted both settlement and myth because they represent thresholds between ecological systems.

    The Quantock fringe, the Blackdown Hills, the Otter valley, and the chalk–clay transition in Dorset all contain clusters of historic estates. These areas combine agricultural productivity with perceptible environmental boundaries, making them ideal settings for stories of disruption or supernatural presence.

    In folklore theory, thresholds are spaces where order becomes negotiable. When catastrophe occurs in such locations, interpretation naturally draws on the symbolism of crossing or transgression.

    Prehistoric monuments and narrative gravity

    The West Country contains numerous Neolithic and Bronze Age earthworks, long barrows, henges, and standing stones. Estates developed near these sites often inherited their aura of antiquity.

    Scholars such as W. G. Hoskins and Oliver Rackham emphasised that prehistoric features remained visible reference points throughout the medieval and early modern periods, shaping settlement patterns and local identity. Antiquarians frequently interpreted these monuments as “pagan,” a term that carried implicit associations with older spiritual forces.

    Where manor houses stood near such sites, later misfortune could be framed as the consequence of disturbing ancient ground. This interpretive pattern appears repeatedly in nineteenth-century folklore collections, where destructive events are explained through narratives of sacred imbalance.

    Woodland as a mythic environment

    Much of the West Country’s historic estate landscape was wooded, particularly on marginal soils. Woodland occupies a central role in European folklore as a space outside ordinary social control.

    In Somerset and Devon traditions, stories of cursed houses often include references to surrounding woods described as “ancient,” “unquiet,” or “haunted.” These descriptions reflect a cultural perception of woodland as both protective and threatening — a repository of memory that predates the house itself.

    Repeated fires at estates surrounded by extensive woodland were therefore interpreted through a symbolic lens in which nature itself participates in judgement. Such narratives echo older European motifs linking forest landscapes with moral testing or supernatural intervention.

    Watercourses and reflective symbolism

    Rivers and streams play a significant role in West Country settlement geography, and many historic houses were sited near water for practical reasons. Yet water also carries symbolic associations with boundary, reflection, and transformation.

    Folklore frequently situates supernatural encounters at bridges, fords, and river bends — places where movement pauses. When fires occurred at nearby houses, stories sometimes linked the event to water spirits, drowned histories, or unseen presences along the river corridor.

    The persistence of these motifs suggests that hydrological features function as narrative anchors, connecting environmental observation with cultural meaning.

    Sacred and ecclesiastical proximity

    The close proximity of manor houses to medieval churches reinforced moral interpretations of disaster. Churches represented spiritual authority; the manor embodied temporal power. When catastrophe struck the latter, communities often interpreted it through the moral framework provided by the former.

    Antiquarian writings frequently note sermons delivered after destructive fires emphasising humility and divine judgement. Even when infernal language appears in folklore, it often operates within a broader Christian moral vocabulary, framing loss as a lesson rather than random misfortune.

    Geological character and psychological perception

    The varied geology of the West Country — chalk downs, red sandstone, clay vales, and granite uplands — contributes to distinct visual atmospheres. Cultural historians argue that landscape character influences emotional response.

    For example, mist-prone valleys or exposed moorland edges create environments conducive to narratives of uncertainty or unease. Estates located in such settings were more likely to attract stories of haunting or curse following destructive events.

    This relationship between physical environment and narrative tone illustrates how occult topography emerges from perceptual as well as historical factors.

    The role of isolation

    Many country houses were intentionally secluded, set within parkland or at some distance from settlements. Isolation reinforces the perception of separateness from everyday life, making catastrophe appear more dramatic and mysterious.

    When a remote manor burned, the physical distance from immediate observation allowed rumours and imaginative interpretations to flourish. Over time, the absence of precise eyewitness accounts encouraged supernatural explanations to fill narrative gaps.

    Temporal layering and the persistence of absence

    Occult topography is fundamentally about temporal depth. Landscapes retain traces of past uses — ridge-and-furrow patterns, hollow ways, boundary banks — that signal continuity even as individual structures vanish.

    Lost manors become part of this layered environment. Their absence is itself a feature, prompting reflection on change and impermanence. Infernal narratives provide a vocabulary for articulating the emotional resonance of disappearance within a landscape otherwise characterised by continuity.

    Comparative perspective

    Similar patterns appear across Britain, but the West Country’s combination of early settlement continuity, high density of historic estates, and strong antiquarian tradition intensifies the phenomenon. The region’s cultural identity emphasises deep history, making it particularly receptive to narratives that connect present events with ancient forces.

    Interpretive framework

    From a scholarly perspective, occult topography can be understood through three interacting dimensions:

    Environmental setting — physical features shaping perception
    Historical layering — accumulation of cultural meanings
    Narrative mediation — folklore and antiquarian interpretation

    Together, these elements create landscapes in which catastrophic events are interpreted symbolically rather than purely materially.

    Concluding reflection

    The concept of occult topography provides a useful lens for understanding why destructive fires at West Country manors so often acquired infernal explanations. The region’s landscapes are not neutral backdrops but active participants in cultural interpretation, carrying memories that extend beyond individual buildings.

    Lost houses become focal points where environmental character, historical depth, and narrative imagination converge. The language of curse or diabolic agency expresses a recognition that certain places feel charged with accumulated meaning — not because of literal supernatural forces, but because they embody the long dialogue between human habitation and the land.

  • Lost manors and infernal agency in the West Country

    Landscape, memory, fire, and the moral imagination of place

    The West Country does not announce its histories loudly; they are found in fragments, in stories told half in passing, in the slight pause someone makes when a lane bends toward an old park wall or a stand of trees older than the fields around them. Across Dorset, Somerset, and Devon, the countryside holds the traces of houses that once anchored local worlds — manors and estates that embodied continuity, hierarchy, and the promise of permanence. Some survive altered, some as shells, and some only in memory.

    Fire is the most abrupt agent of their disappearance. Yet while estate papers and insurance records speak plainly of chimney faults, lightning, or accident, local memory often prefers another language — one of judgement, curse, or the Devil’s hand. This essay explores how destructive fire became entangled with moral imagination, how landscapes shaped interpretation, and why lost houses continue to occupy such a persistent place in the cultural geography of the West Country.

    It is one thing to read of loss in the record, and another to stand where it happened, the ground keeping its own quiet account.

    Fire and the fragility of permanence

    A great house was never merely a dwelling. As Mark Girouard observed, it was a statement about order and continuity, a visible assurance that social arrangements were stable and enduring. The sudden destruction of such a building therefore carried symbolic weight far beyond its physical loss.

    Fire possesses a peculiar narrative force. Unlike decay, which unfolds gradually, fire is sudden and communal. It produces witnesses, urgency, and a moment that becomes fixed in memory. When a manor burned, people gathered, watched, and later recounted. In that retelling, practical causes often gave way to moral interpretation.

    John Collinson, writing in the eighteenth century, noted that rural communities sometimes regarded destructive fires as signs of displeasure, whether divine or infernal, especially where pride or harshness had long been associated with the house. His remark captures not a literal belief so much as an interpretive habit: catastrophe invites meaning.

    Fire, once passed into memory, rarely remains only a practical event.

    The valley at first light

    The valley holds the morning like a shallow bowl, mist resting low over pasture where the river bends in a slow, deliberate arc. Ash trees stand pale against the damp air, their branches showing the shape of the land beyond. A lane drops between hedgebanks thick with moss, the earth dark and fragrant. In the distance, a stone house sits half concealed by trees, its windows catching the first light with a dull glimmer. There is a sense of quiet occupation, not abandonment but pause, as though the landscape is waiting to see what will endure.

    Seen in this way, the physical setting helps explain why such stories endure.

    Repetition and the emergence of curse narratives

    Where fires occurred more than once, folklore deepened. Repeated destruction resisted simple explanation, encouraging stories that framed misfortune as pattern rather than coincidence. Estates with successive losses acquired reputations for being ill-starred, a phrase that gradually shaded into the language of curse.

    The folklorist Ruth Tongue recorded Somerset traditions in which repeated fires were said to indicate that a place had “never settled right,” an expression that conveys unease without explicit supernatural claim. Such phrases reveal how communities negotiate uncertainty, blending observation with interpretation.

    The physical destruction of a house often marks the beginning of its narrative life.

    A burned house in parkland

    The shell stands where the drive once curved, walls rising without roof or floor, their edges softened by weather. Grass has returned to the forecourt, and young sycamores root in what was once a drawing room. From a distance the structure appears almost intact, but closer inspection reveals blackened stone and the absence of glass. Rooks move in the upper walls, their calls echoing where voices once gathered. Nothing here suggests drama now; only a long settling into stillness.

    From these quiet details, the broader pattern becomes easier to recognise.

    Moral economy and the symbolism of judgement

    Rural society historically operated within a moral framework in which landowners were expected to act as custodians as well as proprietors. When they were perceived to fail, whether through neglect or excess, misfortune could be interpreted as retribution.

    Stories linking destructive fires with scandal or moral failing appear frequently in local histories. Such narratives do not necessarily reflect actual belief in supernatural intervention; rather, they express a desire to render social disruption intelligible. The Devil functions here as metaphor — a shorthand for disorder.

    In the space left by certainty, imagination finds room to work.

    Quantock edge

    On the slope where pasture gives way to rough grass, the land opens toward a wide horizon under shifting cloud. Wind moves constantly across the hillside, flattening heather and carrying the sound of distant livestock. A manor lies lower down, partly hidden by trees planted to shelter it from weather that never quite relents. The house seems anchored rather than placed, as if the slope itself required a human presence to complete its shape. Yet the exposed setting hints at the fragility of that occupation.

    The landscape does not replace the archive, but it deepens its meaning.

    Antiquarian mediation and the shaping of legend

    Much of what is now considered traditional folklore was stabilised by nineteenth-century antiquarians who recorded local stories with a mixture of curiosity and romanticism. Their accounts often emphasised haunting and curse, reinforcing the association between ruin and supernatural agency.

    Sabine Baring-Gould remarked that empty houses invite moral drama because imagination seeks to fill silence. His observation highlights how literary interpretation can reshape historical perception, turning contingency into inevitability.

    The story moves from parchment to pasture, from record to recollection.

    Woodland approach

    The track narrows as it enters the wood, light filtering through oak and beech in uneven bands. The ground is soft with leaf litter, and the smell of damp bark is constant. Through the trunks, a glimpse of stone appears — a façade partly obscured, its symmetry interrupted by creeping ivy. The house feels older than its architecture alone would suggest, as though the surrounding trees have absorbed its history and now hold it in quiet custody.

    What appears at first as atmosphere is, in truth, part of the historical fabric.

    Occult topography and landscape memory

    To understand why infernal narratives attach themselves to certain places, it is necessary to consider the concept of occult topography — the way landscapes accumulate symbolic meaning through long habitation and cultural memory.

    The West Country contains dense layers of prehistoric monuments, medieval settlements, and early modern estates. Such layering encourages interpretive frameworks in which misfortune is read as the consequence of deeper forces embedded in place.

    W. G. Hoskins observed that landscapes retain the marks of successive generations, creating environments where past and present coexist. In such settings, catastrophe appears less as isolated event than as part of a continuing dialogue between people and land.

    Beneath each account lies a landscape already rich with association.

    River meadow

    The house sits on slightly raised ground above a flood meadow where the river divides into narrow channels before rejoining downstream. In summer the grass moves like water in the wind. The building’s reflection appears intermittently between reeds, broken by ripples. There is a practical logic to the site — fertile land, access to water — yet also a sense of exposure, as though the house stands in conversation with the slow persistence of the river.

    These impressions return us to the question of how memory attaches itself to place.

    Ruin and the picturesque

    By the late eighteenth century, ruins were increasingly valued for their aesthetic qualities. The picturesque movement encouraged visitors to see decay as a source of reflection rather than merely loss. Burned houses became sites of contemplation, their destruction reframed as transformation.

    William Gilpin described ruins as evoking a pleasing melancholy, a sentiment that shaped how such places were perceived and narrated. Romantic appreciation reinforced supernatural explanations by framing destruction as meaningful.

    Elsewhere, under a different sky, the same themes appear again.

    Moorland margin

    Beyond the last enclosed fields, the land rises toward open moor, the boundary marked by a low stone wall. The air carries the scent of peat and distant rain. A house stands just within the cultivated ground, its windows facing the upland as if keeping watch over a landscape that resists ownership. Weather moves visibly here — shadow and sunlight passing in broad strokes — and the building appears small against the scale of sky and horizon.

    The setting, no less than the event, shapes how loss is understood.

    Modern continuities

    Even in contemporary contexts, fires at historic houses often prompt commentary invoking fate or inevitability. Such language demonstrates that interpretive frameworks established centuries ago remain culturally available.

    Modern heritage discourse emphasises preservation and documentation, yet local storytelling continues to operate alongside official narratives, preserving the emotional dimension of loss.

    Where flame leaves its mark, story soon follows.

    Winter dusk

    The light fades early, turning stone walls grey-blue as frost settles across the ground. Bare branches trace fine lines against the sky, and the house becomes a darker shape within the landscape rather than a focal point. A single window catches the last reflection of sunset before the colour drains entirely. In the stillness, the building appears less like an object and more like a continuation of the land itself.

    Taken together, these fragments suggest a consistent way of seeing.

    The Devil as cultural metaphor

    Scholars such as Owen Davies and Keith Thomas emphasise that supernatural explanations often function as symbolic expressions rather than literal beliefs. The Devil represents disruption — economic change, social conflict, or environmental catastrophe.

    Infernal narratives therefore reveal how communities articulate experience within familiar moral frameworks. They are less about theology than about meaning.

    What remains, after the detail is set aside, is a pattern of memory rooted in place.

    The long view

    From a distant ridge, the pattern of fields, hedgerows, and scattered houses becomes legible as a human arrangement laid over older contours. A manor appears as one element among many, no longer dominant at this scale. The landscape reveals its continuity, while individual structures seem momentary, part of an ongoing cycle of construction and disappearance.

    The houses may be gone or altered, but their presence persists in quieter forms.

    Conclusion

    Lost manors in the West Country occupy a distinctive position within the cultural landscape. Their destruction by fire created moments of rupture that demanded explanation, and folklore supplied narratives of judgement, curse, and infernal agency. These stories reveal how communities interpret change through moral imagination, transforming historical contingency into symbolic drama.

    The persistence of such narratives underscores the enduring power of landscape memory. Even when archival evidence provides practical explanations, the language of the infernal continues to offer a means of expressing the emotional impact of loss. The vanished manor remains present not only as archaeological trace but as story — one in which fire becomes both historical event and cultural metaphor.

    In the end, the landscape holds the longer memory. The land remains, patient as ever, while the stories settle into it like weather into stone.

    Bibliography

    Below is a selected working bibliography for the essay, combining primary antiquarian sources, folklore collections, landscape history, and modern scholarship on country houses, ruin culture, and supernatural belief.

    I’ve prioritised authoritative and commonly cited works relevant to the West Country context.

    Primary antiquarian and historical sources

    Collinson, John. The History and Antiquities of the County of Somerset. Bath: R. Cruttwell, 1791.
    One of the earliest comprehensive county histories; valuable for contemporary interpretations of estates, fires, and local traditions.

    Hutchins, John. The History and Antiquities of the County of Dorset. 3rd ed. Westminster: John Bowyer Nichols, 1861–1874.
    Essential reference for Dorset estates, genealogies, and antiquarian observations including anecdotal material.

    Polwhele, Richard. The History of Devonshire. London: Cadell and Davies, 1793–1806.
    Provides early historical narratives and moral interpretations of estates and landscape.

    Folklore and regional tradition

    Tongue, Ruth L. Somerset Folklore. London: Folklore Society, 1965.
    Important collection of oral traditions including curse motifs and supernatural landscape beliefs.

    Tongue, Ruth L. County Folk-Lore: Somerset. London: Folklore Society, 1965.
    Detailed recording of local narratives and rural belief structures.

    Baring-Gould, Sabine. Devonshire Characters and Strange Events. London: Methuen, 1908.
    Includes anecdotal material reflecting late Victorian interpretations of rural supernatural traditions.

    Simpson, Jacqueline, and Steve Roud. A Dictionary of English Folklore. Oxford: Oxford University Press, 2000.
    Useful for thematic context on supernatural explanation and curse narratives.

    Landscape history and cultural geography

    Hoskins, W. G. The Making of the English Landscape. London: Hodder & Stoughton, 1955.
    Foundational text on historical landscape development and cultural layering.

    Hoskins, W. G. Devon. London: Collins, 1954.
    Regional study with insights into settlement patterns and estate history.

    Rackham, Oliver. The History of the Countryside. London: J. M. Dent, 1986.
    Important for understanding environmental context and long-term rural change.

    Williamson, Tom. The Transformation of Rural England. Exeter: University of Exeter Press, 2002.
    Explores social and economic shifts affecting estates and rural society.

    Country houses and architectural history

    Girouard, Mark. Life in the English Country House: A Social and Architectural History. New Haven: Yale University Press, 1978.
    Definitive study of the social meaning of country houses.

    Mandler, Peter. The Fall and Rise of the Stately Home. New Haven: Yale University Press, 1997.
    Key analysis of decline, preservation, and changing perceptions of country houses.

    Robinson, John Martin. The English Country House. London: Aurum Press, 1986.
    Comprehensive architectural overview.

    Strong, Roy. The Spirit of Britain: A Narrative History of the Arts. London: Pimlico, 1999.
    Useful contextual material on the cultural symbolism of houses and landscape.

    Ruin, memory, and cultural interpretation

    Lowenthal, David. The Past is a Foreign Country. Cambridge: Cambridge University Press, 1985.
    Seminal work on memory, heritage, and historical perception.

    Edensor, Tim. Industrial Ruins: Space, Aesthetics and Materiality. Oxford: Berg, 2005.
    Though focused on industrial sites, provides theoretical framework applicable to ruin interpretation.

    Macfarlane, Robert. The Old Ways. London: Hamish Hamilton, 2012.
    Literary landscape writing illustrating how place accumulates narrative meaning.

    Supernatural belief and interpretation

    Davies, Owen. The Haunted: A Social History of Ghosts. London: Palgrave Macmillan, 2007.
    Authoritative study on the social function of supernatural belief.

    Thomas, Keith. Religion and the Decline of Magic. London: Penguin, 1971.
    Classic analysis of belief systems and their transformation in early modern England.

    Briggs, Katharine. The Folklore of the Cotswolds (relevant comparative material). London: Batsford, 1974.
    Provides broader regional context for rural supernatural traditions.

    Heritage, loss, and preservation

    Delafons, John. Politics and Preservation: A Policy History of the Built Heritage 1882–1996. London: E & FN Spon, 1997.
    Useful for understanding modern attitudes toward ruined houses.

    Jenkins, Simon. England’s Thousand Best Houses. London: Allen Lane, 2003.
    Contextual reference for significance and decline narratives.

    Suggested archival sources for deeper research

    Somerset Heritage Centre — estate papers and parish histories
    Devon Heritage Centre — manor and estate records
    Dorset History Centre — antiquarian manuscripts
    Historic England Archive — fire reports and architectural surveys
    Victoria County History series (Somerset, Devon, Dorset volumes)

  • Subtly Wrong

    Jane Ellery first noticed the change in the sky during the autumn she turned thirty-seven.

    She lived alone in a narrow brick house overlooking the estuary, a place where the river met the sea and the tide exposed long black plains of mud. From her study window the horizon was always low and grey, and on most evenings the clouds flattened themselves against the water like sheets of dull metal. It was a lonely view but a rational one, and Jane—who had spent her career cataloguing sediment cores and oceanographic data—preferred landscapes that behaved according to measurable rules.

    But that year the sky seemed subtly wrong.

    The stars were not brighter or dimmer; they simply appeared older, as though the distances between them had stretched while she slept. Their cold light carried an oppressive patience, the suggestion that they had shone through uncounted ages before humanity arrived and would continue their silent rotation long after the last city had collapsed into dust.

    At first Jane told herself this was fatigue.

    Yet the feeling persisted: a quiet suspicion that the world was not built for human comprehension. The more carefully she examined her data, the more the numbers resembled fragments of an enormous pattern—one too large to perceive except in scattered hints.

    It began with the cores.

    The research institute had asked her to review samples drilled decades earlier from an abyssal basin beyond the continental shelf. The cylinders of sediment, preserved in metal tubes, represented layers of geological time extending back millions of years. Most contained exactly what one would expect: compressed mud, fossil fragments, traces of plankton.

    But at a depth corresponding to an age far older than human civilization, Jane noticed something anomalous.

    The sediment changed structure.

    The grains aligned themselves in thin, repeating ridges that resembled mathematical waves—patterns too regular to be random but too immense to be biological. When she mapped their frequency distribution the ridges formed ratios that echoed astronomical data: orbital cycles, gravitational harmonics, the periodic oscillations of distant stars.

    It was as though the ocean floor had once recorded a signal.

    Not a sound, precisely. A pressure. A rhythm older than language.

    Jane spent nights recalculating the measurements, convinced she had misinterpreted the data. Yet every method returned the same result: the patterns were deliberate. They formed a sequence that repeated across layers separated by millions of years, like a message inscribed slowly into the crust of the planet.

    Her colleagues dismissed the finding as statistical coincidence.

    But Jane could not dismiss it, because she had begun to dream.

    The dreams were not symbolic or surreal in the usual way. They possessed a mechanical clarity, as though she were observing the interior of a vast system. She saw the ocean floor stretching away into darkness, interrupted by shapes that moved with patient inevitability—structures larger than cities that drifted through water thick with silt.

    Sometimes the dreams shifted perspective.

    She would find herself looking upward through miles of water toward the faint glow of the surface. Above that glow lay continents, mountains, forests, cities—all the fragile architecture of human civilization. Yet in the dreams these things seemed temporary, as thin and disposable as the skin of ice forming on a winter pond.

    Beneath them the deeper world waited.

    The dreams did not frighten her at first. They merely carried a quiet implication: humanity had arrived late in the chronology of the Earth.

    Eventually curiosity overcame hesitation.

    Jane requested permission to join an oceanographic survey vessel scheduled to investigate seismic anomalies along the basin. Officially she was there to review sediment stratigraphy, but privately she hoped to confirm what the cores suggested—that something had once disturbed the deep ocean in rhythmic pulses.

    The vessel reached the coordinates after three days of grey water and empty sky.

    The crew deployed an autonomous submersible capable of descending six thousand meters. Its cameras transmitted grainy images of the seafloor: endless fields of dark sediment broken by occasional ridges.

    Jane watched the feed in silence.

    The ridges matched the patterns she had mapped from the cores.

    At first they appeared geological—elongated waves in the mud shaped by ancient currents. But the submersible’s sonar began to register structures beneath them: vast cavities embedded in the crust, arranged in concentric arcs.

    The arcs resembled antennae.

    No one on the ship could explain them.

    The captain assumed they were natural formations. Jane knew they were not, but she found herself strangely reluctant to say so aloud. Some instinct suggested that speaking the idea might make it more real.

    During the following night she remained alone in the control room, reviewing the sonar scans.

    Gradually she realized the arcs were oriented toward the open ocean, aligned with the direction of deep tectonic fractures that stretched across the planet’s mantle. If the formations were indeed antennae—or something analogous—they were not designed to transmit upward toward human civilization.

    They were directed outward.

    Toward the stars.

    A terrible thought unfolded slowly in her mind.

    Perhaps the signal preserved in the sediment had not been a broadcast created by humans or even by terrestrial life. Perhaps it had been part of a much older system—a network embedded within the planet itself.

    The ocean floor, the fractures in the crust, the silent antennae buried beneath miles of water: together they formed a mechanism.

    One that had operated long before humanity evolved.

    In that moment Jane experienced a sensation not of fear but of diminishing importance. Every human concern—politics, culture, memory—seemed suddenly irrelevant against the scale of the system she had uncovered.

    Civilizations were merely temporary phenomena on the surface of a deeper machine.

    The dreams changed after that.

    They no longer showed the distant shapes drifting through the abyss. Instead they revealed a slow awakening within the structures beneath the seabed. The antennae trembled faintly, responding to signals that pulsed through the Earth’s crust like distant thunder.

    Jane understood then that the patterns in the sediment were not relics of the past.

    They were records of repeated cycles.

    Each cycle began with a faint stirring in the deep ocean. Each ended with silence, followed by millions of years of geological calm. Humanity had arisen during one of those quiet intervals and had mistaken the stillness for permanence.

    But the stillness was ending.

    As the ship returned to port Jane stood alone at the stern, watching the grey water stretch toward the horizon. The sky above seemed colder than ever, filled with stars that regarded the Earth with infinite indifference.

    She felt no impulse to warn anyone.

    The truth she had uncovered was too vast to matter in human terms. Whether civilization survived another century or vanished tomorrow would not alter the function of the deeper system beneath the oceans.

    The world continued exactly as before—cities glowing at night, ships crossing the sea, people arguing about trivial concerns.

    Yet Jane knew that beneath the calm surface of the planet something immense had begun to stir.

    And in the immeasurable age of the universe, the brief moment called humanity was already fading, unnoticed by the cold stars turning endlessly overhead.