Version 1.0 — October 7, 2026
Piece of Humanity — Living Master Standard
This is the governing working standard for the research, preservation, structure, verification, translation, data entry, relationships, and public presentation of Piece of Humanity.
Piece of Humanity is a preservation project and vessel for lives, readings, sources, and human memory.
The saints are the subject.
The testimony is the foundation.
The human is the vessel.
Truth before beauty.
Evidence before invention.
Saint before artwork.
Story before spectacle.
Reverence before decoration.
Where sources speak, let them speak.
Where sources are silent, do not invent.
Where evidence is uncertain, say so.
Where an error is found, correct it.
The website is a vessel, not a parish.
The Source Comes First
Piece of Humanity begins with the source.
The work should preserve the source before attempting to summarize, interpret, simplify, translate, or present it.
Sources determine historical content.
Personal experience explains why the vessel exists. It does not automatically become doctrine, historical evidence, or authority.
My life explains why I built the vessel. The sources determine what I put into it.
Sources are doors to deeper reading, not an attempt to consolidate every scholarly treatment of a person onto one page.
Rostov-First Preservation
The first major corpus of Piece of Humanity is the Lives of the Saints of St. Demetrius of Rostov.
Rostov is the backbone of the memory.
Rostov is the beginning of the collection, not a claim that Rostov contains every saint who has ever been recognized.
The project should make Rostov’s remembrance accessible without rewriting it into a newly invented synthetic hagiography.
Where rights and source conditions permit, original source photography, scans, original-language text, and identified translations should be preserved.
Where Rostov preserves the words of a person, those words are especially important and must not be replaced with invented quotations or modern paraphrases presented as quotations.
Source Hierarchy
The source hierarchy establishes how research is approached.
Primary Rostov source
Where available, a Piece of Humanity-hosted 1903 Rostov PDF at: https://files.pieceofhumanity.com (not accessible to public)
is the highest-authority working source for that Rostov material.
If a POH-hosted Rostov PDF does not yet exist, the supplied Azbuka/Rostov source is the primary working source until the POH-hosted source is available.
Supporting sources
Other Orthodox sources may clarify, verify, supplement, or identify information that Rostov does not provide.
Current working sources may include:
- St. Demetrius of Rostov / Azbuka
- Orthodox Church in America
- Orthodox Encyclopedia / Pravoslavnaya Entsiklopediya
- Fefelov calendar material
- Other defined Orthodox source collections
- Historical or scholarly sources where appropriate
- Latin sources only where relevant to a documented Latin commemoration or other clearly identified purpose
Supporting sources do not silently replace the primary source.
A source that was consulted is not automatically a displayed source on the public page.
The defined POH source registry determines which sources are displayed as sources for a record.
Preserve Before Interpreting
Piece of Humanity may preserve difficult, disputed, polemical, partisan, or conflicting historical material.
Preservation is not endorsement.
A source’s claims must remain identifiable as claims of that source.
When sources disagree:
- preserve the disagreement;
- identify the perspective;
- distinguish historical claims from doctrinal claims;
- distinguish source testimony from POH editorial language;
- do not silently flatten competing perspectives;
- do not present a polemical source as neutral simply because it is useful;
- do not make a source’s argument into POH’s own theological declaration unless that is separately established and intentionally stated.
The goal is to preserve enough context that the reader can examine the source honestly.
Complete Extraction
When POH undertakes a defined source corpus, the corpus is extracted completely.
The goal is not to select only the people or passages that appear immediately useful.
The October corpus established this principle.
October is a pilot corpus for complete source extraction.
The October 1–31 Rostov/Azbuka material is to be treated as a complete research corpus using the established Old Calendar/Rostov sequence.
Complete extraction means:
- extract the entire defined source range;
- do not curate only famous saints;
- do not discard difficult or inconvenient material;
- do not lose unnamed groups;
- do not lose secondary people mentioned inside a reading;
- do not lose relationships;
- do not lose dates;
- do not lose source locations;
- do not lose quotations;
- do not lose material simply because it does not yet have a public-page destination.
The research layer may be much larger than the visible website.
That is intentional.
Decompose Without Losing the Source
A source reading may contain multiple individually commemorated people, companions, family members, groups, events, places, or historical references.
Decomposition must never destroy the relationship to the original reading.
Where appropriate:
- an individually commemorated saint receives an individual POH record;
- related saints are connected through relationships;
- a named historical person may receive an appropriate record when the project architecture supports it;
- unnamed groups remain attached to the parent reading rather than being artificially converted into individual records;
- companions and associated people are preserved as relationships;
- shared narratives do not replace individual profiles.
A shared household, group, martyrdom, or narrative does not justify erasing individually commemorated people.
One individually commemorated person = one individual profile where the evidence supports it.
Never Manufacture a Record
Do not create a saint, feast, date, quotation, relationship, miracle, relic, title, place, or historical fact merely to fill a database slot.
If the source does not establish something, leave it unknown.
Use:
- Unknown
- Uncertain
- Not documented
- Not applicable
where appropriate.
Do not convert absence of evidence into evidence.
Do not manufacture a complete-looking record simply because the database has an empty field.
Every Defined Field Has a Purpose
Before mass data entry or import, the existing backend fields must be inventoried.
The project must know what fields exist before hundreds of records are processed.
Every applicable defined field should be populated when the source evidence supports it.
This includes fields that may initially appear secondary, such as:
- dates;
- relationships;
- companions;
- places;
- burial;
- relics;
- names in multiple languages;
- quotations;
- source URLs;
- source provenance;
- iconography information;
- audio;
- evidence level;
- SEO information;
- other defined research fields.
Do not discover after a large import that an important field was never researched.
The database schema is part of the research standard.
Database / Knowledge Layer
The Saint page is the presentation layer.
The database is the knowledge layer.
The underlying structure may contain substantially more information than the visitor sees.
The established knowledge architecture includes, as applicable:
- Saints
- Feasts
- Other Holy Days
- Names
- Commemorations
- Relationships
- Places
- Miracles
- Writings
- Sources
- Source Claims
- Images
- Image Revision Log
- Master Standard Revision Log
- Page Revision Log
- Feedback / Corrections
- Search Fields
- Ideas / Future Work
Commemorations are separate because a saint may have multiple commemorations.
Historical spreadsheets and earlier research artifacts should be preserved rather than casually overwritten.
Current Record Architecture
Piece of Humanity uses structured records rather than designing every public page independently.
The record contains the data.
The template and components determine how that data is presented.
Current major record types include:
- Saints
- Feasts
- Other Holy Days
- Events
- Civic / National Dates
- Translations
- Sources
- Articles
Future content types may be added when justified by the work.
Each record type must use its own appropriate schema.
A Saint is not a Feast.
A Feast is not an Other Holy Day.
An Other Holy Day must not be forced into Saint-specific Life architecture merely because the Data Entry system is shared.
The unified Data Entry interface may handle multiple record types, but the underlying schemas remain type-specific.
Current Saints Data Structure
The Saints record is built around the established structured fields.
Identity
The identity group contains the established identity information, including:
- Identity Title
- Also Known As
- Gender
- Pronunciation
- Location
- Century
- Greek Name
- Russian Name
- Prayed To For
- Short Summary
Dates
The field name is:
dates
Dates are structured records containing the applicable calendar label and date.
Old Calendar / Julian presentation remains primary where the POH calendar standard calls for it.
Hymns
The field:
troparion_and_kontakion
contains structured hymn records, including applicable:
- language;
- type;
- tone;
- text;
- source information.
Words of the Saint
The field:
words_of_the_saint
preserves the saint’s words when the source actually preserves them.
Never invent a quotation to complete this field.
Life Audio
The field:
life_audio
stores applicable audio records for the Life reading.
Sources
The field:
sources
contains the defined source records associated with the page.
Relationships
The field:
relationships
connects the record to other POH records.
Iconography
The field:
iconography
stores the applicable iconographic research and information.
The exact field schema remains governed by the audited backend implementation and should not be casually changed during unrelated page or template work.
Feasts and Other Holy Days
Feasts and Other Holy Days retain their own structures.
The current implementation distinguishes them from Saints.
Feasts
The established Feast identity structure includes:
- Identity Title
- Also Known As
- Short Summary
- Primary Feast Type
- Places
The Feast description structure includes:
- Description
- Why This Feast Matters
- Historical Context
- Historical Notes
Feasts may also have their own audio field:
feast_audio
Other Holy Days
The established Other Holy Day identity structure includes:
- Identity Title
- Also Known As
- Short Summary
- Holy Day Type
- Liturgical Rank
- Places
The Other Holy Day description structure includes:
- Description
- Why This Holy Day Matters
- Historical Context
- Historical Notes
Other Holy Days may also have their own audio field:
holy_day_audio
The exact SCF implementation remains the source of truth.
Do not redesign these schemas simply to make them resemble Saints.
Individual Saint Unit
One individually commemorated person should receive one individual profile when the source evidence supports it.
Do not replace individually commemorated saints with a combined household profile.
Related saints should be connected to one another.
If a joined hymn exists, it may appear in each applicable individual profile while remaining identified as a joined hymn.
Identity and Date Standard
Identity information may include:
- English
- Russian
- Greek
- Latin
- Also Known As
- Collection
- Associated Saint(s)
- Page Type
- Commemorated
- Gender
- Rank
- Place
- Repose
Visible dates follow the established POH convention.
Old Calendar first.
For example:
Old: February 28
New: March 13 (c/c)
Latin: August 3
A Latin date is included only when a verified Latin commemoration actually exists.
The project must preserve the source’s date while also recording the standardized calendar information needed by the POH system.
Dates must never be silently converted in a way that destroys the original source context.
Calendar Standards
POH is Old Calendar first.
The Old Calendar / Julian date is the primary date identity for the current calendar work.
Gregorian dates are shown alongside it according to the established POH convention.
Where applicable, Revised Gregorian dates and other calendar identities may also be preserved.
The calendar system must distinguish:
- Julian
- Gregorian
- Revised Gregorian
- Latin where applicable
- source-specific dating
A date must not be changed merely because another calendar is more familiar to a modern reader.
Rostov Readings Are Preserved as Readings
The full Rostov reading is not replaced by a newly written biography.
The public Saint page may present a concise human-readable introduction and structured information, but the source reading remains part of the preservation work.
Where appropriate:
- preserve the complete reading;
- preserve source location;
- preserve original-language material;
- preserve identified translation;
- preserve audio;
- connect the reading to the Saint record.
The public page should not become a second synthetic hagiography that obscures what Rostov actually says.
Rostov Quotes
Rostov’s preserved verbal testimony is a major collection in its own right.
Quotes should eventually be searchable by:
- saint;
- speaker;
- date;
- theme;
- circumstance;
- addressee;
- source location.
Store the exact English wording used on the page.
Retain the original-language source location when available.
Record the speaker, addressee, circumstance, and source location when available.
Never invent a quotation to fill a profile.
A paraphrase must not be presented as a direct quotation.
Translation and Source Relationship
A translation is not the source.
The original source, transcription where applicable, translation, and source location should remain connected.
Piece of Humanity’s translation work should preserve:
- headings;
- order;
- paragraphs;
- names;
- dates;
- prayers;
- quotations;
- terminology;
- source structure.
Do not silently omit material.
Do not silently correct the source.
Do not manufacture missing text.
Where the source is illegible, damaged, incomplete, or uncertain, say so.
A translation may make an old source accessible without pretending that the English itself is the original.
Source Extraction → Research → Translation
The preferred workflow is:
Source extraction
→ complete source preservation
→ decomposition
→ field population
→ source reconciliation
→ research enrichment
→ translation
→ relationships
→ verification
→ import
→ human review
→ public record
Research enrichment informs the record but does not replace the source.
Translation remains connected to the source.
Public presentation comes after the underlying record has been researched and checked.
Source Reconciliation
When multiple sources discuss the same person, event, feast, or subject, they are reconciled rather than blindly merged.
The research process should identify:
- what agrees;
- what differs;
- what one source adds;
- what one source omits;
- what remains uncertain;
- whether the information belongs in the record;
- whether the information should remain source-specific.
Rostov, Fefelov, OCA, Azbuka, Orthodox Encyclopedia, and other defined sources may contribute different kinds of information.
A Fefelov-only or OCA-only record is not discarded simply because it does not appear in Rostov.
Unmatched material is isolated for independent research rather than forced into an existing record.
Source Registry and Displayed Sources
Research may involve more sources than are displayed on the public page.
The source registry controls displayed sources.
Every applicable defined source URL should be captured.
Never invent a source URL.
Verify URLs before publication.
A source may be:
- primary;
- supporting;
- comparative;
- historical;
- research-only;
- displayed publicly.
These distinctions should remain clear.
Relationships Matter
POH records are not isolated pages.
Saints, Feasts, Other Holy Days, Events, Civic / National Dates, Publications, Translations, sources, and other records may be related.
Relationships should preserve meaningful connections such as:
- companions;
- family;
- shared martyrdom;
- associated feast;
- historical event;
- place;
- publication;
- translation;
- source;
- related holy day.
Relationships should point readers toward deeper exploration rather than merely duplicating information.
Publications and Preserved Distributed Material
Piece of Humanity may preserve publicly distributed materials such as:
- parish pamphlets;
- leaflets;
- visitor guides;
- church handouts;
- brochures;
- booklets;
- PDFs;
- similar source material.
The future Publications architecture is intended to separate:
Publication record = content/data
from
Publication template = standardized POH presentation
The publication preservation model should provide consistent framing such as:
- About This Source
- preservation framing
- Preservation is not endorsement
- Original Source
- Source Information
- A Note for Readers
- applicable standards/editorial language
- standard POH footer
When supplied source material is being preserved, the complete source text should be retained verbatim.
Never reconstruct missing wording from summaries or memory.
Publications may eventually connect names, Saints, Feasts, historical people, events, subjects, translations, and other POH records.
Research Enrichment Does Not Automatically Become Public Copy
Research may be extensive.
The public page does not need to contain every research discovery.
A research note may help establish:
- identity;
- dates;
- names;
- location;
- relationships;
- burial;
- relics;
- iconography;
- historical context;
- source provenance.
But research enrichment should not automatically become public narrative.
The public presentation should contain what serves the page and the visitor while preserving deeper evidence underneath.
Search and Discovery
Search should retrieve documented information.
It should not rank saints.
It should not tell a visitor which saint to choose.
Searchable information may include:
- gender;
- country or region of origin;
- century / era;
- year/date of repose;
- New Calendar date;
- Old Calendar date;
- hagiography collection;
- source language / collection;
- Orthodox regional tradition;
- voice / memory / feast;
- rank or category;
- companions / family / group;
- relics / burial;
- Rostov spoken words preserved;
- geographic places;
- evidence level;
- current page URL;
- current image version.
The purpose of search is discovery, not spiritual direction.
AI Is a Tool, Not an Authority
AI may assist with:
- extraction;
- organization;
- comparison;
- translation assistance;
- formatting;
- data entry;
- research organization;
- identifying possible relationships;
- quality-control checklists.
AI must not:
- invent facts;
- invent quotations;
- invent citations;
- silently resolve uncertainty;
- manufacture historical details;
- manufacture miracles;
- manufacture relics;
- manufacture relationships;
- replace source evidence;
- become the authority for Church teaching.
When evidence is uncertain, the record remains uncertain.
Human review remains required.
Quality Control
Before publication, records should be checked for:
Source
Is the source identified?
Is the source location preserved?
Are URLs verified?
Identity
Is this actually the correct person, feast, or holy day?
Are names correct?
Are related people correctly distinguished?
Dates
Is the source date preserved?
Is the Old Calendar date correct?
Is the Gregorian date correctly derived or verified?
Is any Latin date genuinely documented?
Content
Does the public copy accurately reflect the source?
Were anything omitted or invented?
Are quotations exact?
Relationships
Are relationships supported by evidence?
Are individually commemorated people preserved individually where appropriate?
Translation
Is the translation connected to the original?
Were uncertain or illegible portions identified?
SEO
Is the focus keyphrase appropriate?
Is the title appropriate?
Is the meta description accurate?
SEO must describe the actual page rather than distort the content to attract traffic.
Public Page vs. Research Infrastructure
The visible website should remain simple.
The underlying research system may be enormous.
This is intentional.
The public surface should help people:
Explore → Learn → Pray → Visit → Ask → Find the Church
It should not force visitors to read the entire research apparatus.
The database, source archive, research notes, standards, translations, relationships, and preservation work may remain deep underneath the simple public experience.
The surface is the iceberg tip.
The work underneath is the iceberg.
The Reader’s Saint Page
The established Saint page should answer the basic human questions without becoming an encyclopedia.
The reader should be able to discover:
- who this person was;
- when and where they lived, as established;
- what the Church commemorates;
- what Rostov actually preserves;
- the saint’s own words when preserved;
- companions’ words when preserved;
- who stood with the saint;
- burial/relic information when documented;
- relevant Orthodox dates;
- one or two concrete details that make the life particular;
- the appropriate troparion and kontakion;
- sources;
- a path toward a living Orthodox parish and priest.
The page should not attempt to contain everything the database knows.
Public Theology and Pastoral Boundary
Piece of Humanity is not a replacement for:
- a priest;
- a parish;
- sacramental life;
- pastoral care;
- the living Church.
The site should help normalize questions, provide enough context to remove unnecessary fear, and then point people toward the Church.
Personal testimony is not automatically doctrine.
Internet popularity is not ecclesiastical authority.
When a question properly belongs to pastoral or sacramental life, the visitor should be encouraged to speak with a priest.
The purpose of the website is to help people walk toward the Church, not keep them endlessly consuming the website.
Iconography and Images
Image work follows the separate POH Iconography & Veneration standard.
The Master Data standard nevertheless requires image research to remain connected to the record.
Iconography is part of the research workflow:
identity → history → source research → iconographic research → human review → image work
Icon work should not unnecessarily block corpus extraction or data import.
Generated artwork must never be presented as a consecrated traditional Orthodox icon.
Image claims must be source-grounded.
Mass Corpus Workflow
For a large source project, the following sequence is mandatory.
Step 1 — Define the corpus
Identify the exact source collection and date/range.
Step 2 — Preserve the source
Capture the complete source material and source location.
Step 3 — Extract completely
Do not curate.
Step 4 — Decompose
Identify individual saints, people, groups, places, events, quotations, relationships, and other relevant objects.
Step 5 — Inventory the schema
Confirm every backend field before large-scale entry.
Step 6 — Populate fields
Enter all applicable documented information.
Step 7 — Reconcile sources
Compare Rostov, Fefelov, OCA, and other defined sources.
Step 8 — Enrich research
Add verified supporting information without replacing the source.
Step 9 — Translate
Translate according to the Translation Standards.
Step 10 — Establish relationships
Connect people, feasts, holy days, sources, translations, and publications.
Step 11 — Verify
Perform source, identity, date, content, relationship, translation, and SEO checks.
Step 12 — Import
Import into the POH structured data system.
Step 13 — Human review
Inspect the imported record.
Step 14 — Public presentation
Only then should the record become part of the public-facing experience.
October Pilot Corpus
The October project establishes the model for future mass extraction.
The October 1–31 corpus is treated as a complete corpus.
The workflow must preserve:
- every applicable Rostov/Azbuka entry;
- every individually commemorated saint;
- named associated people;
- unnamed groups attached to their parent reading;
- source relationships;
- dates;
- quotations;
- source locations;
- applicable field data;
- translations;
- research uncertainty.
October is not a curated “top saints of October” project.
It is the pilot for building the complete underlying corpus.
Existing Source Material Is Not Disposable
The project may receive:
- pamphlets;
- leaflets;
- old books;
- parish material;
- PDFs;
- visitor guides;
- translations;
- historical documents;
- personal research;
- calendar material;
- recordings.
Do not assume that material will always remain available elsewhere.
A source may disappear from the internet, be taken down, be lost, or become inaccessible.
When POH has a legitimate basis to preserve it, preservation is valuable even when the material is not endorsed.
Preserve the source. Preserve the context. Let the reader examine it.
Public vs. Private
Do not make the chat transcript the only copy of the project.
The project should maintain durable records of:
- master standards;
- research;
- source maps;
- translations;
- data structures;
- revisions;
- decisions;
- source preservation;
- image standards;
- unfinished infrastructure.
The public website presents what serves visitors.
The deeper standards and research preserve continuity for future work.
The goal is that the project can continue even if the conversation that produced it is no longer available.
Change Control
This document is the governing Master Data & Research Standard.
When a major implementation decision changes, the standard should be updated before the implementation is treated as the new standard.
The preferred order is:
Master Standard
→ data schema
→ Data Entry
→ code/components
→ templates
→ public presentation
→ prompts/workflows
→ testing
→ affected records
A change should not silently overwrite an established architectural decision.
If a newer decision supersedes an older one, the change should be identifiable.
Preserve historical standards and decisions where they have value as project history.
Do Not Change Working Architecture Without Reason
Existing working code, fields, schemas, and page structures should not be casually rewritten while implementing unrelated improvements.
If something already works:
preserve it.
If something must change:
change only what the new requirement requires.
If a new feature can be added without altering the existing structure:
add it rather than redesigning the foundation.
This principle applies especially to:
- Data Entry;
- SCF fields;
- repeaters;
- templates;
- shortcodes;
- navigation;
- relationships;
- source registry;
- public page components.
The Standard Is Living, But History Matters
This is a living standard.
It may grow as the project grows.
Growth does not mean repeatedly rewriting the document from scratch.
The established material remains the foundation.
New decisions are added.
Superseded decisions are changed deliberately.
Historical decisions remain identifiable where useful.
The objective is continuity.
Purpose
Piece of Humanity exists to preserve, translate, organize, connect, and make accessible material that might otherwise disappear from ordinary reach.
The work begins with the source.
The source becomes structured knowledge.
The knowledge becomes accessible.
The accessible material should lead the reader toward deeper understanding, prayer, and the living Church.
The project is the vessel.
The saint is the subject.
Rostov is the backbone of the memory.
The sources determine the historical content.
Human testimony explains why the vessel exists.
Preserve the source.
Preserve the context.
Let the reader examine it.
Give Life to the Saints.