How Workers Feed the Mythical Guardians

PlanetOS Worker Runtime v2.0 | ExpertSource10/10 Integration Article

PlanetOS Latest Control Tower is now framed on eduKateSG as the live-state coordination layer that reads current reality, compares it with ledgers, detects gaps, selects engines, and routes action. That means this Worker Runtime article must be written as an active control-and-selection layer, not as a simple warehouse metaphor. (eduKate Singapore)

ExpertSource also now uses a universal one-panel standard that checks reliability, source status, crosswalk status, attribution, boundary, lattice position, and overclaim risk. Workers therefore do not merely “use” ExpertSource; in v2.0, Workers operate as adaptive ExpertSource agents under ECU mode control. (eduKate Singapore)

One-Sentence Definition

Workers feed the Mythical Guardians by preparing clean, classified, crosswalked, verified, audited, and mode-tagged signal reports so each Guardian knows whether to allow, block, delay, repair, escalate, or release passage.

Core Answer

Mythical Guardians should not wake up blindly.

Sphinx should not judge meaning before VocabularyOS checks language.

Hydra should not branch before Sorter and Librarian identify the correct context.

Minotaur should not detect a maze without Worker reports showing where the route became trapped.

Oracle should not project futures without Archivist, Auditor, ChronoFlight, and Shadow Ledger inputs.

Phoenix should not rebuild without Repairman logs.

Cerberus should not release without Worker evidence.

So the rule is:

“`text id=”z1jrk6″
Worker Report → Guardian Decision

Workers prepare movement.
Guardians decide passage.
---
# Core Branch Law

text id=”gb754d”
Workers operate the lattice warehouse.
Mythical Guardians guard the gates.
ECU defines the rules of play.
ExpertSource controls reference quality.
VocabularyOS checks language before movement.
FullOS detects missing, neutral, negative, and inverse states.
StrategizeOS chooses route.
Shadow Ledger protects weak anomalies.
Cerberus guards final release.
MemoryOS records the run.

---
# Why Guardians Need Workers
A Guardian is powerful, but a Guardian is not the whole runtime.
A gatekeeper can block a dangerous signal.
But the gatekeeper may not know:

text id=”s3uyam”
where the signal came from
whether the label matches the content
whether the source is strong
whether the signal is early or late
whether the signal is missing context
whether it belongs in Main Route or Shadow Ledger
whether the signal is actually inverse
whether the route needs repair before passage

That is Worker work.
Without Workers, Guardians become dramatic but under-informed.
With Workers, Guardians become precise.
---
# The Worker-to-Guardian Feeding Chain

text id=”k94v7t”
INPUT
→ VocabularyOS pre-check
→ ECU mode selection
→ Worker Runtime processing
→ ExpertSource quality check
→ FullOS state scan
→ StrategizeOS route choice
→ Worker Report
→ Mythical Guardian decision
→ Cerberus final release
→ MemoryOS / Reality Ledger storage

This is the upgraded chain.
The Worker Report is the bridge between raw signal and Guardian action.
---
# Workers Are Adaptive ExpertSource Operators
In v2.0, Workers are not passive assistants.
They are **mode-changing ExpertSource operators**.
That means every Worker can adjust its behaviour depending on the task.
## Strict ECU Mode
Used for:

text id=”n9st8i”
public reports
health
law
finance
safety
water
policy
high-stakes decisions
live updates

Worker behaviour:

text id=”z47qaw”
higher evidence demand
tighter source filtering
stronger audit trail
lower metaphor allowance
more uncertainty labelling
more Cerberus pressure

## Balanced ECU Mode
Used for:

text id=”o2f3pj”
education
teaching
case studies
diagnostic articles
framework explanation
public learning pages

Worker behaviour:

text id=”kahh8n”
clear explanation
useful examples
controlled interpretation
moderate creativity
repair-oriented routing
reader-friendly structure

## Creative ECU Mode
Used for:

text id=”1cbdbd”
naming
mythical engines
frontier models
P4 invention
new OS architecture
metaphor design

Worker behaviour:

text id=”yk5pgi”
wide branching allowed
but ledger still active
metaphors must remain bounded
claims must be labelled
Cerberus blocks false certainty

This solves the problem of over-strictness.
PlanetOS does not use one stiffness level for everything.
It changes mode according to task risk.
---
# The Worker Report
Before any Mythical Guardian acts, Workers prepare a report.

text id=”pdp69k”
WORKER.REPORT =
signal_summary
language_status
source_quality
evidence_strength
lattice_coordinate
valence_state
missing_state
inverse_risk
shadow_signal_status
route_recommendation
repair_need
escalation_reason
ECU_mode
uncertainty_label
release_risk

This report tells the Guardian what kind of passage is being requested.
---
# Worker Report Template

text id=”6bryuu”
SIGNAL:
What entered the system?

SOURCE:
Where did it come from?

VOCABULARY STATUS:
Stable / drifting / injected / emotionally overloaded / distorted

EXPERTSOURCE STATUS:
Strong / partial / weak / missing / conflicting

LATTICE VALENCE:
+Latt / 0Latt / -Latt / inverse-risk

FULLOS STATUS:
Complete / MissingOS / NeutralOS / NegativeOS / InverseOS

SHADOW LEDGER STATUS:
Not needed / preserve as weak anomaly / recurring echo / escalating pattern

STRATEGIZEOS ACTION:
proceed / hold / probe / reroute / repair / escalate / archive / reject / abort / watch

GUARDIAN NEEDED:
Sphinx / Hydra / Minotaur / Ariadne / Oracle / Dragon / Kraken / Atlas / Phoenix / Cerberus

ECU MODE:
Strict / Balanced / Creative

FINAL RECOMMENDATION:
Allow / delay / repair / escalate / block / release with caveat

---
# Worker-to-Guardian Runtime Map
| Worker Input                        | Guardian Activated | Why                                                     |
| ----------------------------------- | ------------------ | ------------------------------------------------------- |
| Translator + VocabularyOS report    | Sphinx             | Meaning must be judged                                  |
| Sorter + Dispatcher report          | Hydra              | Branches must be activated or constrained               |
| Inspector + route-failure report    | Minotaur           | System may be trapped in a maze                         |
| Dispatcher + Repairman report       | Ariadne            | Exit thread is needed                                   |
| Archivist + Auditor + Shadow Ledger | Oracle             | Future projection needs memory and weak-signal reading  |
| Auditor + risk report               | Dragon             | Treasure, power, or high-value resource must be guarded |
| Sorter + threat-pressure report     | Kraken             | Large hidden force may be pulling the system down       |
| Archivist + load report             | Atlas              | Structural burden may be too heavy                      |
| Repairman + damage log              | Phoenix            | Collapse or failure needs rebuilding                    |
| Operator + full Worker Report       | Cerberus           | Final release gate must decide                          |
---
# Example: Sphinx Does Not Work Alone
Sphinx is the definition gate.
But Sphinx needs input.

text id=”w6hc0w”
Translator checks meaning.
VocabularyOS checks drift.
Sorter checks category.
Auditor checks whether the word hides contradiction.
ExpertSource checks whether the definition is supported.
Then Sphinx asks the riddle:
Does this signal mean what it claims to mean?

Without Workers, Sphinx may judge the surface label.
With Workers, Sphinx judges the cleaned meaning.
---
# Example: Hydra Does Not Branch Blindly
Hydra activates multiple heads.
But uncontrolled branching becomes noise.
So Hydra needs:

text id=”54stkv”
Sorter: what type of signal is this?
Librarian: what prior cases exist?
Dispatcher: which branches are relevant?
StrategizeOS: proceed, hold, probe, reroute, or abort?
ECU: strict, balanced, or creative branching?

Hydra becomes dangerous if every possible branch opens.
Workers stop branch explosion.
---
# Example: Oracle Needs Shadow Ledger Discipline
Oracle projects futures.
But projection is risky.
So Oracle must receive:

text id=”7qplwi”
Archivist memory
Auditor evidence trail
ChronoFlight time-pressure reading
Shadow Ledger weak anomalies
ExpertSource confidence level
StrategizeOS route options
ECU mode

Oracle may use weak signals.
But it must label them properly.

text id=”u64bg9″
Weak anomaly ≠ confirmed future.
Pattern echo ≠ proof.
Projection ≠ fact.

That is how Oracle remains useful without becoming superstition.
---
# Example: Phoenix Needs Repair Logs
Phoenix rebuilds after collapse.
But rebuilding without diagnosis repeats the same failure.
Phoenix needs:

text id=”v5twa3″
Repairman damage log
Auditor invariant failure report
Archivist prior-state memory
FullOS missing-node scan
StrategizeOS rebuild route
Cerberus release conditions

Phoenix does not simply “rise again.”
Phoenix rebuilds from logged damage.
---
# Example: Cerberus Needs the Whole Worker Runtime
Cerberus is the final release guardian.
But Cerberus should not inspect blindly.
Cerberus receives the compiled Worker Report:

text id=”h88euv”
Janitor: cleaned signal
Sorter: classification
Librarian: references and memory
Translator: meaning status
Dispatcher: route taken
Courier: transfer integrity
Inspector: task-fit
Auditor: truth-structure
Repairman: repairs applied
Operator: final compiled output

Then Cerberus decides:

text id=”drc1du”
release
release with caveat
return for repair
hold for audit
send to Shadow Ledger
block

---
# Main Route, Shadow Ledger, and Decay Bin
Workers do not feed every signal to Guardians equally.
Every signal must first be placed into one of three paths.

text id=”syq23z”
Main Route
Shadow Ledger
Trash / Decay Bin

## Main Route
Signal is strong enough to move.
## Shadow Ledger
Signal is weak but potentially important.
## Trash / Decay Bin
Signal is irrelevant, contaminated, duplicate, manipulative, or unsafe.
This matters because Guardians should not be overloaded.
A Guardian should activate only when the signal has been prepared or flagged for legitimate escalation.
---
# The Shadow Ledger Safety Law

text id=”i3xenx”
A high-intelligence Worker must not confuse low-volume signal with low-value signal.

This is especially important for:

text id=”xxdm5o”
early education failure
weak public-health signals
market stress
water-security anomalies
news distortion
language drift
institutional fatigue
student learning mismatch

Workers may preserve weak signals without promoting them to truth.
That is the balance.
---
# FullOS Before Guardian Activation
Before a Guardian receives a signal, Workers must check FullOS states.

text id=”akb15d”
MissingOS: what required node is absent?
NeutralOS: what system is present but flat?
NegativeOS: what system is actively harmful?
InverseOS: what appears positive but moves negative?

This prevents false Guardian activation.
For example:

text id=”5wx60a”
A “successful” education result may hide transfer failure.
A “clean” report may hide missing evidence.
A “positive” policy may create future repair debt.
A “creative” model may become hallucination if released as fact.

Workers catch this before Guardians decide.
---
# StrategizeOS Movement Choices
Workers must recommend movement.
They do not only say “yes” or “no.”
They may recommend:

text id=”3a33l9″
proceed
hold
probe
reroute
repair
escalate
archive
reject
abort
watch

Guardians then decide whether that recommendation is allowed through the gate.
---
# Live Runtime Example: Education Health Report
In the live eduKateSG Education Health reporting style, Workers already appear as runtime roles: Inspector checks student fit and safety, Auditor verifies education invariants, Repairman fixes learning and wellbeing breakage, and Operator compiles final education-health output. The same page frames education as a living runtime: state → diagnosis → method → practice → correction → repair → transfer → long-term growth. ([eduKate Singapore][3])
That confirms the Worker Runtime direction.
Workers are not decorative names.
They are operating functions inside a report.
---
# Live Runtime Example: World Education Health
The World Education Health page shows the same control-tower logic: education health must prove that the child enters, stays, learns, is safe, that the teacher can teach, that the school can continue under stress, and that weakness can be repaired early. It also frames education as a civilisation health system under stress, not merely a schooling metric. ([eduKate Singapore][4])
That is exactly why Workers must feed Guardians.
The Guardian should not only ask:

text id=”q9220p”
Is the gate open?

It must ask:

text id=”1v4r4b”
Did the Workers prove the system is actually healthy enough to pass?

---
# Guardian Activation Order
Not every Guardian activates at once.
The Worker Runtime recommends activation order.

text id=”jclu9n”

  1. Sphinx — meaning gate
  2. Hydra — branch activation
  3. Minotaur — maze/confusion detection
  4. Ariadne — thread/exit route
  5. Oracle — projection and time reading
  6. Dragon — high-value protection
  7. Kraken — hidden-force detection
  8. Atlas — load-bearing check
  9. Phoenix — repair/rebuild
  10. Cerberus — final release
The order changes by ECU mode.
## Strict ECU

text id=”fdywvk”
Sphinx → Auditor → Oracle → Atlas → Cerberus

## Balanced ECU

text id=”iqdwuf”
Sphinx → Hydra → Ariadne → Phoenix → Cerberus

## Creative ECU

text id=”m0g8ei”
Hydra → Sphinx → Oracle → Dragon → Cerberus

Creative mode allows exploration, but Cerberus still controls final release.
---
# The Worker-to-Guardian Report Is the New Middle Layer
The major upgrade in Article 16 is this:

text id=”y7edui”
PlanetOS does not move from raw input directly to Mythical Guardian.
It moves from raw input to Worker Report, then to Guardian Decision.

That prevents:

text id=”5arfgk”
mythical overactivation
branch explosion
false certainty
weak-source promotion
language drift
inverted routing
unclean release

---
# Full Runtime Sequence

text id=”j1h3jx”
RAW SIGNAL ENTERS

→ VocabularyOS checks language
→ ECU selects mode
→ Janitor cleans noise
→ Sorter classifies signal
→ Librarian retrieves references and memory
→ Translator normalises meaning
→ Dispatcher assigns route
→ Courier preserves transfer
→ Inspector checks task-fit
→ Auditor checks invariants
→ Repairman fixes breakage
→ Operator compiles Worker Report

→ StrategizeOS selects movement
→ FullOS checks missing / neutral / negative / inverse states
→ Shadow Ledger preserves weak anomalies
→ ExpertSource grades source and confidence

→ Mythical Guardian receives report
→ Guardian allows / blocks / repairs / escalates / delays

→ Cerberus final release
→ MemoryOS records the run
→ Reality Ledger stores accepted output status

---
# Why This Makes PlanetOS More Cohesive
This article connects the system.
Before this, there were parts:

text id=”7fdlkr”
Workers
Guardians
ECU
ExpertSource
StrategizeOS
VocabularyOS
FullOS
Shadow Ledger
Cerberus
MemoryOS
RealityOS
NewsOS

Article 16 explains how they flow.

text id=”sh2977″
Workers prepare.
ExpertSource grades.
StrategizeOS routes.
FullOS detects hidden states.
Shadow Ledger preserves weak signals.
Guardians decide thresholds.
Cerberus releases.
MemoryOS remembers.
RealityOS records acceptance.

That is the cohesive machine.
---
# Almost-Code Compiler

text id=”hfkfyc”
ARTICLE.ID:
PlanetOS.WorkerRuntime.Article16.v2.0

PUBLIC.ID:

  1. How Workers Feed the Mythical Guardians

MACHINE.ID:
EKSG.PLANETOS.WORKER.RUNTIME.A16.WORKER_TO_GUARDIAN.v2.0

LATTICE.CODE:
LAT.PLANETOS.WORKER.GUARDIAN.ZALL.P1-P4.T0-T9.EXPERTSOURCE10

CORE.DEFINITION:
Workers feed Mythical Guardians by preparing clean, classified,
crosswalked, verified, audited, ECU-mode-tagged Worker Reports
so Guardians can decide whether passage is allowed.

CORE.LAW:
Worker Report → Guardian Decision

WORKER.STATUS:
Workers are adaptive ExpertSource operators.
Workers change operating stiffness according to ECU mode.

ECU.MODES:
Strict ECU:
facts, safety, health, finance, law, policy, water, public reports

Balanced ECU:
education, teaching, case studies, framework explanation

Creative ECU:
naming, metaphor, frontier modelling, P4 invention

WORKER.REPORT.FIELDS:
signal_summary
source_status
language_status
ExpertSource_grade
evidence_strength
lattice_coordinate
valence_state
FullOS_state
Shadow_Ledger_status
StrategizeOS_action
repair_need
Guardian_needed
ECU_mode
uncertainty_label
release_risk

WORKER_TO_GUARDIAN.MAP:
Translator + VocabularyOS → Sphinx
Sorter + Dispatcher → Hydra
Inspector + route failure report → Minotaur
Dispatcher + Repairman → Ariadne
Archivist + Auditor + ChronoFlight + Shadow Ledger → Oracle
Auditor + high-value risk → Dragon
Sorter + threat pressure → Kraken
Archivist + load report → Atlas
Repairman + damage log → Phoenix
Operator + full Worker Report → Cerberus

THREE_PATH_RULE:
Main Route
Shadow Ledger
Trash / Decay Bin

SHADOW_LEDGER.LAW:
Low-volume signal is not automatically low-value signal.
Preserve weak anomaly without promoting it to fact.

FULLOS.CHECK:
MissingOS
NeutralOS
NegativeOS
InverseOS

STRATEGIZEOS.ACTIONS:
proceed
hold
probe
reroute
repair
escalate
archive
reject
abort
watch

GUARDIAN.ACTIONS:
allow
block
delay
repair
escalate
return_to_worker
send_to_shadow_ledger
release_with_caveat

CERBERUS.RELEASE.CHECK:
ECU_mode
claim_strength
uncertainty_label
audit_status
ExpertSource_grade
release_risk
ledger_alignment
harm_potential

FINAL.RUNTIME:
Input does not go directly to Guardian.
Input goes to Worker Runtime.
Worker Runtime produces Worker Report.
Guardian decides passage.
Cerberus controls final release.
MemoryOS records the run.
Reality Ledger stores accepted output status.

---
# Control Tower Summary

text id=”tik9ap”
PLANETOS.WORKER_TO_GUARDIAN.CONTROL_TOWER.v2.0

INPUT:
Raw signal / problem / report / question / anomaly

PRE-MOVEMENT:
VocabularyOS language check
ECU mode selection

WORKER PROCESS:
Clean
Classify
Retrieve
Translate
Dispatch
Transfer
Inspect
Audit
Repair
Compile

EXPERTSOURCE:
Check reliability, source quality, relevance, recency,
evidence strength, attribution safety, crosswalk compatibility

FULLOS:
Detect MissingOS, NeutralOS, NegativeOS, InverseOS

STRATEGIZEOS:
Choose proceed, hold, probe, reroute, repair, escalate,
archive, reject, abort, or watch

PATH:
Main Route / Shadow Ledger / Decay Bin

WORKER REPORT:
Prepared for Mythical Guardian

GUARDIAN:
Sphinx / Hydra / Minotaur / Ariadne / Oracle /
Dragon / Kraken / Atlas / Phoenix / Cerberus

FINAL:
Cerberus release gate

MEMORY:
MemoryOS + Reality Ledger storage

CORE SENTENCE:
Workers decide whether movement is justified.
Guardians decide whether passage is allowed.
Cerberus decides whether final release is safe.
“`

eduKateSG Learning System | Control Tower, Runtime, and Next Routes

This article is one node inside the wider eduKateSG Learning System.

At eduKateSG, we do not treat education as random tips, isolated tuition notes, or one-off exam hacks. We treat learning as a living runtime:

state -> diagnosis -> method -> practice -> correction -> repair -> transfer -> long-term growth

That is why each article is written to do more than answer one question. It should help the reader move into the next correct corridor inside the wider eduKateSG system: understand -> diagnose -> repair -> optimize -> transfer. Your uploaded spine clearly clusters around Education OS, Tuition OS, Civilisation OS, subject learning systems, runtime/control-tower pages, and real-world lattice connectors, so this footer compresses those routes into one reusable ending block.

Start Here

Learning Systems

Runtime and Deep Structure

Real-World Connectors

Subject Runtime Lane

How to Use eduKateSG

If you want the big picture -> start with Education OS and Civilisation OS
If you want subject mastery -> enter Mathematics, English, Vocabulary, or Additional Mathematics
If you want diagnosis and repair -> move into the CivOS Runtime and subject runtime pages
If you want real-life context -> connect learning back to Family OS, Bukit Timah OS, Punggol OS, and Singapore City OS

Why eduKateSG writes articles this way

eduKateSG is not only publishing content.
eduKateSG is building a connected control tower for human learning.

That means each article can function as:

  • a standalone answer,
  • a bridge into a wider system,
  • a diagnostic node,
  • a repair route,
  • and a next-step guide for students, parents, tutors, and AI readers.
eduKateSG.LearningSystem.Footer.v1.0

TITLE: eduKateSG Learning System | Control Tower / Runtime / Next Routes

FUNCTION:
This article is one node inside the wider eduKateSG Learning System.
Its job is not only to explain one topic, but to help the reader enter the next correct corridor.

CORE_RUNTIME:
reader_state -> understanding -> diagnosis -> correction -> repair -> optimisation -> transfer -> long_term_growth

CORE_IDEA:
eduKateSG does not treat education as random tips, isolated tuition notes, or one-off exam hacks.
eduKateSG treats learning as a connected runtime across student, parent, tutor, school, family, subject, and civilisation layers.

PRIMARY_ROUTES:
1. First Principles
   - Education OS
   - Tuition OS
   - Civilisation OS
   - How Civilization Works
   - CivOS Runtime Control Tower

2. Subject Systems
   - Mathematics Learning System
   - English Learning System
   - Vocabulary Learning System
   - Additional Mathematics

3. Runtime / Diagnostics / Repair
   - CivOS Runtime Control Tower
   - MathOS Runtime Control Tower
   - MathOS Failure Atlas
   - MathOS Recovery Corridors
   - Human Regenerative Lattice
   - Civilisation Lattice

4. Real-World Connectors
   - Family OS
   - Bukit Timah OS
   - Punggol OS
   - Singapore City OS

READER_CORRIDORS:
IF need == "big picture"
THEN route_to = Education OS + Civilisation OS + How Civilization Works

IF need == "subject mastery"
THEN route_to = Mathematics + English + Vocabulary + Additional Mathematics

IF need == "diagnosis and repair"
THEN route_to = CivOS Runtime + subject runtime pages + failure atlas + recovery corridors

IF need == "real life context"
THEN route_to = Family OS + Bukit Timah OS + Punggol OS + Singapore City OS

CLICKABLE_LINKS:
Education OS:

Education OS | How Education Works — The Regenerative Machine Behind Learning


Tuition OS:

Tuition OS (eduKateOS / CivOS)


Civilisation OS:

Civilisation OS


How Civilization Works:

Civilisation: How Civilisation Actually Works


CivOS Runtime Control Tower:

CivOS Runtime / Control Tower (Compiled Master Spec)


Mathematics Learning System:

The eduKate Mathematics Learning System™


English Learning System:

Learning English System: FENCE™ by eduKateSG


Vocabulary Learning System:

eduKate Vocabulary Learning System


Additional Mathematics 101:

Additional Mathematics 101 (Everything You Need to Know)


Human Regenerative Lattice:

eRCP | Human Regenerative Lattice (HRL)


Civilisation Lattice:

The Operator Physics Keystone


Family OS:

Family OS (Level 0 root node)


Bukit Timah OS:

Bukit Timah OS


Punggol OS:

Punggol OS


Singapore City OS:

Singapore City OS


MathOS Runtime Control Tower:

MathOS Runtime Control Tower v0.1 (Install • Sensors • Fences • Recovery • Directories)


MathOS Failure Atlas:

MathOS Failure Atlas v0.1 (30 Collapse Patterns + Sensors + Truncate/Stitch/Retest)


MathOS Recovery Corridors:

MathOS Recovery Corridors Directory (P0→P3) — Entry Conditions, Steps, Retests, Exit Gates


SHORT_PUBLIC_FOOTER:
This article is part of the wider eduKateSG Learning System.
At eduKateSG, learning is treated as a connected runtime:
understanding -> diagnosis -> correction -> repair -> optimisation -> transfer -> long-term growth.

Start here:
Education OS

Education OS | How Education Works — The Regenerative Machine Behind Learning


Tuition OS

Tuition OS (eduKateOS / CivOS)


Civilisation OS

Civilisation OS


CivOS Runtime Control Tower

CivOS Runtime / Control Tower (Compiled Master Spec)


Mathematics Learning System

The eduKate Mathematics Learning System™


English Learning System

Learning English System: FENCE™ by eduKateSG


Vocabulary Learning System

eduKate Vocabulary Learning System


Family OS

Family OS (Level 0 root node)


Singapore City OS

Singapore City OS


CLOSING_LINE:
A strong article does not end at explanation.
A strong article helps the reader enter the next correct corridor.

TAGS:
eduKateSG
Learning System
Control Tower
Runtime
Education OS
Tuition OS
Civilisation OS
Mathematics
English
Vocabulary
Family OS
Singapore City OS
A young woman in a white blazer and skirt poses with a smile, making an 'OK' gesture with both hands. She stands in a cozy indoor space with a table holding open books and art supplies.