Sylvan Employment Campus Working Placement
Accepted working structure
After the approximately ten-year protected reserve is exhausted, Sylvan enters the employment stage. He begins in a low-level operations-support position inside a large multi-environment campus. The setting may resemble a major technology company, university, large-footprint institution, or hybrid of those forms. The exact employer remains open.
The campus spans many environments and functions, giving Sylvan legitimate reasons to move through different physical, social, technical, administrative, and restricted spaces. He advances from the low-level position through increasingly difficult training levels. Each level expands responsibility, access, and the range of situations his Luminai must learn to navigate.
This structure gives Samuel many opportunities for attacks, plans, and plots without requiring a new employer for every environment. Samuel can target employment, income, reputation, relationships, safety, permissions, projects, and training outcomes. Exact duties, departments, advancement gates, and attacks will be refined during later development.
First multi-year objective
For the first few years, Sylvan must work with the same group of people. Samuel tries to turn them against him and use their conflicts, vulnerabilities, perceptions, and decisions to make Sylvan fail. Sylvan and his Luminai must learn how to navigate the shared environment and help the group become stable enough to function.
The objective is not to dominate, optimize, or covertly manage the other people. A successful result must preserve their independent choices while building sufficient trust, cooperation, resilience, and shared competence. This gives the employment stage an ensemble cast and creates room for friendships, rivalries, misunderstandings, loyalty, betrayal, humor, grief, and other emotionally consequential interactions.
Legacy group and breeding-scandal connection
Some members of the initial group are legacies or descendants of contained criminals, deliberately positioned in advance by that faction in preparation for Sylvan's employment environment. Some are themselves consequences of Samuel's unauthorized breeding and bloodline manipulation.
Samuel intends to redirect responsibility for his system onto Sylvan, George, and selected people within Sylvan's group. The exact alleged acts, division of blame, forged evidence, and degree of George's responsibility remain unresolved. This conspiracy makes the group both a real human community and part of Samuel's prepared framing operation.
The initial group contains three awareness levels:
- people who know nothing and believe their ordinary family histories;
- people who know something is wrong but have been given false explanations;
- a small number deliberately positioned to manipulate the group and help frame Sylvan.
Awareness does not determine moral responsibility by itself. The exact knowledge, choices, coercion, and actions of each person must be developed individually.
Department scale
The group is Sylvan's actual department inside the large campus company, not an obviously artificial training cohort. It has ten people including Sylvan, a realistic department size for the institution. The department remains together through a multi-year operating and training period, allowing ordinary workplace dependence to carry the hidden process test.
Working distribution:
- six members who believe their ordinary family histories;
- two who know something is wrong but possess false explanations;
- two deliberately positioned to manipulate the department and support the framing operation.
The exact distribution may be refined while designing individual characters, but ten establishes the working ensemble size.
Department function — accepted working direction
The ten-person group works as a campus operations response department. Its responsibilities can include moving specialized equipment and supplies, preparing spaces, supporting events and projects, solving inventory or facility problems, coordinating among laboratories, offices, workshops, public areas, and restricted zones, and responding to unusual operational failures.
The work must remain varied, campus-wide, and project-based. It cannot resemble a postal processing facility or read as a disguised account of the author's employment. Avoid mail or parcel sorting as the central activity, conveyor-centered production, delivery-route imitation, or a repetitive shift-floor structure substantially modeled on a postal factory. Everyday observations may inspire isolated human pressures, interactions, physical details, or institutional behavior, but the fictional workplace must transform and recombine them into a distinct organization.
First shared assignment — accepted working direction
The department's first major assignment is supporting the infrastructure setup for an expansion of the campus data center. The ten members are not the primary designers of the computing architecture. They provide the cross-campus physical and operational support that allows specialized teams to complete the expansion.
Their work can include coordinating access, equipment and material arrival, temporary spaces, contractor support, safety boundaries, inventory, documentation, schedules, facilities requests, testing preparation, and communication among data-center specialists, utilities, security, laboratories, offices, and campus management. Exact duties remain open until the company and characters are refined.
The assignment requires the whole department because no one member possesses every access path, relationship, skill, schedule, or area of responsibility. Samuel can attack the seams between those responsibilities and make an ordinary support failure appear deliberate or catastrophic.
Development-order constraint
Do not design individual attacks, planted actions, altered records, scene beats, or similar mechanics yet. Complete the employment arc's macro structure first: the campus's civilizational purpose, the major training levels, the purpose of each level, the group's progression, and the resulting state that leads toward terminal control. Attack specifics come later after the structure establishes what the department must accomplish.
Author-directed pause
Pause this branch before defining the campus company's purpose, training ladder, characters, attacks, or additional assignments. The current brainstorming began disconnecting the employment environment from the overall story.
At the next desktop session, begin by mapping Sylvan's active relationship with Samuel at the moment Sylvan enters employment:
- what has already happened between them;
- how much each knows about the other;
- how much influence Samuel possesses;
- how Samuel can interact with Sylvan despite remote containment;
- which intermediaries and systems Samuel can use;
- what Samuel needs Sylvan to do or fail to do;
- what Sylvan and his Luminai have already learned;
- what changes over the employment stage.
Then derive the employer, department, training structure, and group function from that conflict map. Existing campus ideas remain accepted working material, not a mandate to preserve details that fail the integrated story test.
Meeting the people gives Sylvan one of his first routes into the breeding scandal. He notices resemblances, repeated traits, family inconsistencies, impossible relationships, behavioral echoes, or other patterns that create suspicion. Those observations are clues, not proof. Parentage and command responsibility require authenticated records and an independently challengeable evidence chain. The descendants are people with their own agency, not public exhibits.
Current best entry role
Working: campus operations response. Possible duties include moving specialized equipment and supplies, preparing spaces, responding to work orders and unusual failures, assisting events and projects, and supporting multiple departments. The role appears low-status but creates unusually broad contact with the campus.
Open
- Exact employer and campus purpose.
- Sylvan's starting title and duties.
- The department's final in-world name.
- Training levels and advancement evidence.
- Exact data-center expansion scope and support tasks.
- Samuel's attack strategy at macro level; specific attacks are deferred until the employment arc is structurally mapped.
- Who belongs to the initial group and why each person is there.
- Which members occupy each of the three awareness levels and how those states change.
- What Samuel intends to blame on Sylvan, George, and specific group members.
- Which observed pattern first raises Sylvan's suspicion and what later evidence can authenticate it.
- What makes the group unstable before Samuel intervenes.
- What observable result counts as a stable group without requiring conformity or control.
- Which relationships survive beyond the first training level.
- Which areas are initially restricted.
- Individual employment-stage attacks, deferred until macro structure is complete.