eduKate Singapore

VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Next useful routeCanonical hubHELP

ENGLISH OS v0.1 — Z1 Sentence Coordinate Grid (Almost-Code)

This is the “grammar engine” as a lattice: generate sentences by coordinate, not rules.

Start Here: https://edukatesg.com/english-os-v0-1-civos-compatible/

Z1.0 — Canonical Sentence Coordinate (SCC)

ID: ENG.Z1.SCC.v0_1

SCC = [Mood] × [Polarity] × [Voice] × [Time] × [Aspect] × [State] × [Frame] × [VerbClass]

Axis enums (LOCK)

  • Mood ∈ {STMT,QYN,QWH,IMP,COND}
  • Polarity ∈ {POS,NEG}
  • Voice ∈ {ACT,PASS}
  • Time ∈ {PAST,NOW,FUT}
  • Aspect ∈ {SIMPLE,ONGOING,COMPLETE,HABIT}
  • State ∈ {STATIC,DYNAMIC,TRANSITION}
  • Frame ∈ {SVO,SVC,SV,SVOO,SVOC,SVA}
  • VerbClass ∈ {BE,HAVE,DO,MODAL,LEX}

Grammar = selecting the correct auxiliary spine for a coordinate.
Errors = illegal coordinate or wrong spine.

Z1.1 — Clause Skeleton Library (Frames)

ID: ENG.Z1.FRAMES.v0_1

SV (intransitive)

  • Template: S + V
  • Example: “Birds fly.”

SVO (transitive)

  • Template: S + V + O
  • Example: “She opened the door.”

SVC (copular)

  • Template: S + COP + C
  • COP usually be / seem / become
  • Example: “He is tired.” / “She became a doctor.”

SVA (adverbial complement)

  • Template: S + V + A
  • Example: “They live in Singapore.”

SVOO (ditransitive)

  • Template: S + V + O1 + O2
  • Example: “He gave her a gift.”

SVOC (object complement)

  • Template: S + V + O + C
  • Example: “They made him captain.”

Z1.2 — Auxiliary Spine Rules (the engine)

ID: ENG.Z1.AUXSPINE.v0_1

Core principle

Every finite clause is:

[Front] + [AuxSpine] + [MainVerbForm] + [Complements]

Where AuxSpine is built from:

  • Tense carrier: did / do / does / am-is-are / was-were / have-has / will / modal
  • Aspect marker:
  • be + V-ing (ONGOING)
  • have + V-en (COMPLETE)
  • Voice marker:
  • be + V-en (PASSIVE)

Verb forms (LOCK)

  • V0 base: go
  • Vs 3rd singular: goes
  • Ved past: went
  • Ving -ing: going
  • Ven past participle: gone

Z1.3 — Legal Build Tables (by coordinate family)

1) ACT / DYNAMIC / ACTIVE (most common)

ID: ENG.Z1.TABLE.ACTIVE_DYNAMIC.v0_1

Mood = STMT, Polarity = POS, Voice = ACT, Frame = SVO/SV

TimeAspectAuxSpineMainVerbFormExample
NOWSIMPLE(none) / do/does only for emphasisV0/Vs“She writes.”
PASTSIMPLE(none)Ved“She wrote.”
FUTSIMPLEwillV0“She will write.”
NOWONGOINGam/is/areVing“She is writing.”
PASTONGOINGwas/wereVing“She was writing.”
FUTONGOINGwill beVing“She will be writing.”
NOWCOMPLETEhave/hasVen“She has written.”
PASTCOMPLETEhadVen“She had written.”
FUTCOMPLETEwill haveVen“She will have written.”

✅ This table alone covers most “tense” use without a tense chart.

2) NEGATION (Polarity = NEG)

ID: ENG.Z1.TABLE.NEGATION.v0_1

Rule (LOCK)

Negation attaches to first auxiliary.
If there is no auxiliary, English inserts DO.

No Aux → insert DO (do/does/did) + NOT + base verb
Has Aux → Aux + NOT (or contraction) + rest

Examples by coordinate:

  • NOW + SIMPLE: “She does not write.”
  • PAST + SIMPLE: “She did not write.”
  • NOW + ONGOING: “She is not writing.”
  • NOW + COMPLETE: “She has not written.”
  • FUT + SIMPLE: “She will not write.”

3) YES/NO QUESTIONS (Mood = QYN)

ID: ENG.Z1.TABLE.QYN.v0_1

Rule (LOCK)

Questions invert first auxiliary with the subject.
If no auxiliary exists, insert DO.

Examples:

  • NOW + SIMPLE: “Does she write?”
  • PAST + SIMPLE: “Did she write?”
  • NOW + ONGOING: “Is she writing?”
  • NOW + COMPLETE: “Has she written?”
  • FUT: “Will she write?”

4) WH-QUESTIONS (Mood = QWH)

ID: ENG.Z1.TABLE_QWH.v0_1

Rule (LOCK)

WH word occupies Front position.
Then apply QYN inversion.

Examples:

  • Object: “What did she write?”
  • Time: “When did she write?”
  • Place: “Where does she live?”
  • Subject (special): no do-support inversion needed
  • “Who wrote the letter?” (WH = subject)

5) PASSIVE VOICE (Voice = PASS)

ID: ENG.Z1.TABLE_PASSIVE.v0_1

Rule (LOCK)

Passive = be + Ven with tense/aspect on be.

TimeAspectAuxSpineExample
NOWSIMPLEam/is/are“The door is opened.”
PASTSIMPLEwas/were“The door was opened.”
FUTSIMPLEwill be“The door will be opened.”
NOWONGOINGam/is/are being“The door is being opened.”
PASTONGOINGwas/were being“The door was being opened.”
NOWCOMPLETEhave/has been“The door has been opened.”
PASTCOMPLETEhad been“The door had been opened.”

Z1.4 — STATE Constraints (Static vs Dynamic)

ID: ENG.Z1.STATE_CONSTRAINTS.v0_1

Static verbs (examples)

know, believe, like, love, want, need, understand, own, belong

Constraint

Static verbs typically reject ONGOING aspect in standard usage:

  • ✅ “I know.”
  • ✅ “I have known him for years.”
  • ❌ “I am knowing.” (illegal move)

Dynamic verbs

run, write, build, eat

  • allow ONGOING naturally.

Transitional verbs

become, get, turn, grow

  • often model “change of state”
  • commonly pair with complements:
  • “He became tired.”

Z1.5 — Modal Layer (ability / obligation / probability)

ID: ENG.Z1.MODALS.v0_1

Modals act as the tense carrier (no -s, no do-support).

Core modals: can, could, may, might, must, should, would

Examples:

  • POS STMT: “She can write.”
  • NEG: “She cannot write.”
  • QYN: “Can she write?”
  • Past-meaning: use could / would / should or periphrastic forms:
  • “She could write.” (past ability / conditional)
  • “She had to write.” (past obligation)

Z1.6 — Sentence Coordinate Drill Generator (the practice engine)

ID: ENG.Z1.DRILLGEN.v0_1

Drill format (LOCK)

Pick 1 coordinate slice and generate 12 sentences:

Slice = [Mood fixed] × [Polarity fixed] × [Time varies] × [Aspect varies]
Keep: Frame=SVO, Voice=ACT, State=DYNAMIC

Example slice:
Mood=QYN, Polarity=NEG, Voice=ACT, Frame=SVO, State=DYNAMIC

Generate:

  • “Did she not write…?”
  • “Does she not write…?”
  • “Is she not writing…?”
  • “Has she not written…?”
  • “Will she not write…?”
    etc.

This creates muscle memory of legal moves.

Z1.7 — Z1 Sensor Pack (Sentence Engine Instrument Panel)

ID: ENG.Z1.SENSORS.v0_1

Per 150–200 word sample:

  • S1.IllegalCoordinateCount (wrong aux / wrong verb form)
  • S2.AuxMissingOrExtra (do-support missing / double-aux)
  • S3.TenseCarrierError (did + Ved, has + Ved, etc.)
  • S4.AgreementLeak (he write / they writes)
  • S5.QuestionInversionLeak
  • S6.NegationPlacementLeak
  • S7.PassiveBuildLeak (missing “be/been/being”)
  • S8.RunOnFragmentRate (boundary control)

Target: reduce S1–S7 to near zero under timing.

Z1.8 — Failure Mode Tags (for the Repair Router)

ID: ENG.Z1.FAILTAGS.v0_1

  • FT.Z1.DO_SUPPORT (missing do/does/did)
  • FT.Z1.DO_DOUBLE (did + past verb)
  • FT.Z1.AUX_CHAIN (wrong have/be order)
  • FT.Z1.VFORM (wrong V0/Vs/Ved/Ving/Ven)
  • FT.Z1.INVERSION (question order wrong)
  • FT.Z1.NEG_ATTACH (not placed wrong)
  • FT.Z1.STATE_ILLEGAL (static verb in ongoing)
  • FT.Z1.FRAME_MISMATCH (picked wrong SVO/SVC etc.)

Copy-Paste: WordPress Spec Block (Z1)

ENG_OS.Z1.v0_1

  • SCC = Mood×Polarity×Voice×Time×Aspect×State×Frame×VerbClass
  • Engine: AuxSpine builds tense/aspect/voice; errors are illegal coordinates
  • Tables: Active-Dynamic / Negation / QYN / QWH / Passive / Modals
  • Constraints: Static verbs block ongoing; dynamic allows
  • DrillGen: coordinate slice → 12 sentences/day
  • Sensors: illegal coordinate count, aux errors, inversion, neg attach, V-form, agreement
  • FailTags: DO_SUPPORT, AUX_CHAIN, VFORM, INVERSION, NEG_ATTACH, STATE_ILLEGAL, FRAME_MISMATCH

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors