Add Ethosism ecosystem surfaces

Author: CharGrnmn

README.md

@@ -6,8 +6,31 @@ Ethos is the monorepo for the Ethosism canon. It keeps the core Ethos book, comp
 
 1. Read the core book at [books/ethos](books/ethos).
 2. Browse the full library in [books](books).
-3. Work on the public website in [web](web).
-4. Use the repo-local writing guidance in [books/ethos/docs/writing-guide.md](books/ethos/docs/writing-guide.md).
+3. Use the practice layer in [practice](practice).
+4. Use the handbook and governance docs in [docs](docs).
+5. Work on the public website in [web](web).
+6. Use the repo-local writing guidance in [books/ethos/docs/writing-guide.md](books/ethos/docs/writing-guide.md).
+
+## Ecosystem Surfaces
+
+The public site now exposes the ecosystem as more than a book index.
+
+- `/start`: what Ethosism is, where to read first, and how to practice this week.
+- `/practice`: daily rule, weekly rule, discernment worksheet, repair script, and facilitator guide.
+- `/ethra`: public Ethra orientation with starter dictionary search, corpus examples, and term proposal guidance.
+- `/governance`: change control for canon, practice, language, publication, and local use.
+- `/handbook`: compact integrated path through Ethosism, Ethra, practice, and governance.
+
+Repo-owned source artifacts:
+
+- [practice/README.md](practice/README.md)
+- [practice/weekly-rule.md](practice/weekly-rule.md)
+- [practice/discernment-worksheet.md](practice/discernment-worksheet.md)
+- [practice/repair-script.md](practice/repair-script.md)
+- [practice/facilitator-guide.md](practice/facilitator-guide.md)
+- [docs/governance.md](docs/governance.md)
+- [docs/ethra-public-interface.md](docs/ethra-public-interface.md)
+- [docs/ethosism-handbook.md](docs/ethosism-handbook.md)
 
 ## Book Layout
 
@@ -33,10 +56,15 @@ The old top-level `chapters/`, `docs/`, and `src/` directories are retained for
 
 The Astro site in `web/` publishes the library to `ethosian.info`.
 
+- `/start`: public reader path and first-week practice.
 - `/books`: full Ethosism library.
 - `/books/<book-slug>`: one book's reading sequence.
 - `/books/<book-slug>/chapters/<chapter-slug>`: namespaced chapter route.
 - `/chapters`: legacy route for the core Ethos book.
+- `/practice`: practice layer.
+- `/ethra`: Ethra learning and proposal surface.
+- `/governance`: ecosystem governance.
+- `/handbook`: integrated handbook.
 
 Chapter slugs are namespaced by book, so repeated filenames such as `00-introduction.md` do not collide.
 

docs/ethosism-handbook.md

@@ -0,0 +1,94 @@
+# Ethosism Handbook
+
+This handbook is the shortest integrated path through Ethosism, Ethra, practice, and governance.
+
+## What Ethosism Is
+
+Ethosism is a secular, theology-compatible framework for living with purpose, integrity, reciprocal responsibility, and a long view. It tests moral claims against reality, consequences, role reversal, honest alignment between values and behavior, and the duties created by relationship, inheritance, trust, and future impact.
+
+## What Ethosism Is Not
+
+Ethosism is not a church, therapy system, political party, identity label, or replacement for professional care. It can be used by religious and nonreligious people, but it should not be used to claim spiritual authority over others.
+
+## The First Five Moves
+
+1. Read the introduction.
+2. Name one fact you have been avoiding.
+3. Choose one real duty.
+4. Repair one concrete harm.
+5. Record what should be remembered.
+
+## The Ethos Method
+
+When making a moral judgment, ask:
+
+1. What is true?
+2. Who is affected?
+3. What would role reversal reveal?
+4. What duty exists?
+5. What action is proportionate?
+6. What harm must be prevented or repaired?
+7. What should be remembered for the future?
+
+## The Ethra Layer
+
+Ethra is the language project attached to Ethosism. It makes moral and relational distinctions grammatically visible.
+
+Key starter distinctions:
+
+- `kan`: can, capacity.
+- `lun`: may, permission.
+- `wen`: want, desire.
+- `vel`: choose, agency.
+- `cel`: should, fitting obligation.
+- `dom`: owe, debt.
+- `dov`: vow, binding speech.
+- `mor`: inherited duty.
+- `ten`: entrusted duty.
+- `ren`: repair.
+
+Ethra matters because vague language permits vague responsibility. A complete ecosystem needs words that make duty, repair, scope, address, and memory harder to hide.
+
+## One-Week Start
+
+Use the weekly rule:
+
+1. Attention.
+2. Duty.
+3. Repair.
+4. Stewardship.
+5. Service.
+6. Learning.
+7. Review.
+
+By the end of the week, you should have one recorded fact, one named duty, one started repair, one stewardship action, one service action, one correction, and one memory for the next week.
+
+## Group Practice
+
+Groups should read one passage, apply one worksheet to one concrete case, choose one bounded action, and review one previous commitment.
+
+Groups should not demand confession, create dependence on a leader, or pretend to adjudicate matters that require professional or institutional process.
+
+## Governance
+
+Ethosism changes through source-controlled proposals, review, and versioned publication. Canon, practice, Ethra terminology, and local use each have different authority.
+
+When in doubt, preserve the distinction between:
+
+- Text.
+- Interpretation.
+- Experiment.
+- Local custom.
+- Personal opinion.
+
+## Thirty-Day Path
+
+Week 1: Use the weekly rule.
+
+Week 2: Read the core Ethos introduction and one domain framework relevant to your life.
+
+Week 3: Complete a discernment worksheet and a repair script.
+
+Week 4: Host or join one reading/practice session and record the next duty.
+
+At the end of thirty days, continue only what produced clearer truth, more reliable conduct, real repair, and stronger memory.

docs/ethra-public-interface.md

@@ -0,0 +1,67 @@
+# Ethra Public Interface
+
+The Ethra public interface is the web-facing learning and search layer for the Ethra language project.
+
+The source of truth remains the Ethra repository. The public interface should expose enough of that source for readers, learners, and term contributors to use Ethra without opening YAML files or running the CLI first.
+
+## MVP Surface
+
+1. Grammar guide: phonology, SVO order, particles, moral agency, relational address, and scope.
+2. Starter dictionary: searchable terms with meaning, type, category, and example sentence.
+3. Corpus search: examples grouped by track and cultural function.
+4. Proposal packet: a structured path for root, compound, register, and corpus proposals.
+5. Source links: direct paths to specs, docs, corpus, validation, and CLI commands.
+
+## Data Sources
+
+- `spec/particles.yaml`
+- `spec/pronouns.yaml`
+- `spec/lexicon.yaml`
+- `spec/examples.yaml`
+- `spec/corpus.yaml`
+- `spec/compounds.yaml`
+- `spec/governance.yaml`
+- `docs/grammar.md`
+- `docs/moral-grammar.md`
+- `docs/relational-grammar.md`
+- `docs/dictionary.md`
+- `docs/corpus.md`
+
+## Proposal Packet
+
+Every public proposal form should collect:
+
+- Submitter name or handle.
+- Concept field.
+- Proposed kind.
+- Domain.
+- Register.
+- Components or root family.
+- English gloss.
+- Ethra candidate.
+- Example sentence.
+- Cultural function.
+- Existing-term collision notes.
+- Review notes.
+
+The web form should not directly mutate Ethra specs. It should produce a reviewable packet or issue body.
+
+## Search Behavior
+
+Search should match:
+
+- Ethra word.
+- English meaning.
+- Category.
+- Register.
+- Example sentence.
+- Corpus track.
+- Cultural note.
+
+Results should always show the source category and link back to the Ethra repository.
+
+## Current Public Page
+
+The Ethos site includes `/ethra` as a lightweight public learning interface. It is intentionally small and curated until the full Ethra spec can be bundled or served as static search data.
+
+The next implementation step is to generate a compact JSON index from Ethra specs during deployment.

docs/governance.md

@@ -0,0 +1,101 @@
+# Ethosism Governance
+
+This document defines the first public governance layer for Ethosism: how canon, practice, Ethra terms, and community use change without losing coherence.
+
+## Authority Layers
+
+1. Canon: source texts in `books/` and the core Ethos chapters.
+2. Practice: worksheets, scripts, session formats, and applied guides in `practice/`.
+3. Language: Ethra specs, corpus, lexicon, dictionary, style, and governance files in the Ethra repository.
+4. Publication: website, print outputs, release packets, and handoff evidence.
+5. Local use: study groups, households, facilitators, and institutions applying the material.
+
+Lower layers may adapt to context, but they must not contradict higher layers without proposing a change.
+
+## Change Status
+
+Every substantive proposal should be labeled with one of these statuses.
+
+- Draft: private or early work, not relied on publicly.
+- Proposed: ready for review against canon, evidence, and practice use.
+- Experimental: usable in bounded trials with clear review criteria.
+- Accepted: incorporated into the relevant source of truth.
+- Deprecated: retained for history but no longer recommended.
+- Rejected: reviewed and declined with reasons.
+
+## Canon Changes
+
+Canon changes require:
+
+1. A statement of the problem.
+2. The affected files and passages.
+3. The proposed replacement.
+4. Reasoning from Ethosism principles.
+5. Expected practical consequences.
+6. Compatibility notes for related books and practice materials.
+7. A review record.
+
+No canon change should be accepted merely because it sounds better. It must clarify truth, duty, consequence, repair, formation, or stewardship.
+
+## Practice Changes
+
+Practice changes require:
+
+1. A concrete use case.
+2. A failure mode the practice addresses.
+3. A short version usable by newcomers.
+4. Boundaries and referral conditions.
+5. A feedback method.
+
+Practices should be small enough to complete, specific enough to review, and humble enough to revise.
+
+## Ethra Term Governance
+
+Ethra terms should be governed as part of the language project, not improvised by popularity.
+
+Term proposals should include:
+
+- English field or concept.
+- Proposed kind: root, derived term, compound, particle, register rule, corpus entry, or style rule.
+- Domain and register.
+- Components and etymology.
+- Example sentence.
+- Cultural function.
+- Collision check against existing roots, compounds, and terms.
+- Review outcome.
+
+The Ethra CLI already supports governed term proposal packets. Web-facing proposal forms should collect the same information before a term enters review.
+
+## Community Governance
+
+Local groups and facilitators may host study, practice, service, and repair sessions. They may not claim ownership of Ethosism, invent binding doctrine, require confession, sell spiritual authority, or override professional/legal/medical processes.
+
+Facilitators are responsible for:
+
+1. Clear session boundaries.
+2. Text-grounded interpretation.
+3. Non-coercive participation.
+4. Protection of private information.
+5. Referral out when a matter exceeds the group's competence.
+6. Transparent correction when they mislead, overreach, or mishandle harm.
+
+## Versioning
+
+Use semantic language for public releases even when the repository itself has ordinary Git history.
+
+- Major: changes that alter doctrine, canon structure, or governance authority.
+- Minor: new books, practices, Ethra domains, or public workflows.
+- Patch: corrections, clarifications, links, metadata, and non-doctrinal edits.
+
+Each public release should identify the canon commit, website commit, Ethra version if relevant, and any practice/governance changes.
+
+## Review Questions
+
+Before accepting an ecosystem change, ask:
+
+1. Does this make reality easier to see?
+2. Does this clarify duty rather than hide it?
+3. Does this reduce avoidable harm?
+4. Does this improve repair when harm occurs?
+5. Does this preserve memory across time?
+6. Does this resist personality cults, coercion, and vague self-help drift?

practice/README.md

@@ -0,0 +1,49 @@
+# Ethos Practice System
+
+The practice system turns Ethosism from a reading project into a repeated way of seeing, choosing, acting, repairing, and remembering.
+
+It is not a sacrament, therapy protocol, legal process, or substitute for medical care. It is a practical rule of life for people who want the canon to shape ordinary conduct.
+
+## Core Loop
+
+1. See reality clearly.
+2. Name the duty in front of you.
+3. Choose a bounded action.
+4. Repair what your action harms or reveals.
+5. Record what should be remembered.
+
+Ethra names the loop compactly: attention, duty, vow, repair, memory. The point is not to speak Ethra in daily life before you understand it. The point is to let Ethra expose distinctions that English often leaves vague.
+
+## Daily Rule
+
+Use this five-minute practice once a day.
+
+1. What fact am I avoiding?
+2. Who is affected by my next choice?
+3. What duty is actually mine?
+4. What repair is overdue?
+5. What one action will I complete before the day ends?
+
+Write the answer in one or two sentences. Do not turn daily practice into a diary performance.
+
+## Weekly Rule
+
+Use [weekly-rule.md](weekly-rule.md) for the seven-day starter path. It covers attention, duty, repair, stewardship, service, learning, and review.
+
+## Worksheets
+
+- [discernment-worksheet.md](discernment-worksheet.md): use before hard choices, public claims, commitments, and conflicts.
+- [repair-script.md](repair-script.md): use after harm, betrayal, negligence, or failed responsibility.
+- [facilitator-guide.md](facilitator-guide.md): use for study groups, household practice, and local gatherings.
+
+## Minimum Viable Practice
+
+A newcomer should be able to begin without reading the entire canon.
+
+1. Read the introduction.
+2. Use the daily rule for seven days.
+3. Complete one discernment worksheet.
+4. Make one repair that is actually owed.
+5. Join or host one reading session using the facilitator guide.
+
+The system is working when practice produces clearer speech, more reliable conduct, fewer unowned harms, and stronger memory across time.