Network Leadership required [Server Team] Narrative Team Suggestion

[Dusk]

"Preserving the story, refining the world."​

What does this suggestion change/add/remove:
This suggestion introduces a new branch called the Narrative Team, a small, dedicated team focused on improving written storytelling, lore consistency, and event documentation across both the UK and USA SCP-RP servers.
The Narrative Team would function as a support division under the Event Team, working closely with the Content Team. Its goal is simple: to ensure every storyline, log, and event on Civil Networks feels connected, professional, and true to SCP’s tone and established server lore.
Instead of being a new layer of management, the Team would be a hands-on creative group that helps polish, plan, and document the written side of SCP-RP, including:

• Writing and reviewing event storylines and dialogue for the Event Team.
• Updating old department lore or helping write new lore blurbs.
• Proofreading in-game documents, announcements, or new SCP entries for consistency and immersion.
• Bridging the gap between community-created lore and original Civil Networks worldbuilding.

---

Has something similar been suggested before? If so, why is your suggestion different?:
Writing help has existed informally through volunteers or community submissions, but it has never been structured, reviewed, or integrated into the staff workflow.
The Narrative Team is different because it introduces a formalized, staff-integrated writing system. It connects directly to existing CN divisions (Event, Content, and Resources) without requiring new ranks or permissions. Everything the Team does still goes through standard approval channels, but with the added benefit of a dedicated, organized, and professional writing group.

---

How the Narrative Team Will Function:

1. Structure and Roles
The Team would have two clear ranks:

• Senior Writers – Experienced members who review, edit, and finalize writing before submission to Event or Server Leadership. They ensure lore accuracy and tone consistency.
• Junior Writers – Entry-level members who assist with event scripts, lore documents, and creative drafts under guidance from Senior Writers, with promotion based on reliability and quality.

No “Lore Overseer” or leadership position is needed, the Team fits naturally under Event Team supervision.

---

2. Team Placement and Oversight
The Narrative Team operates under the Event Team umbrella, similar to how the Gamemasters or Content Team branches function:

• Event Team Leads oversee and approve final lore or event drafts.
• Resources Team collaborates to update documentation, guides, and department writeups.
• Content Team requests lore assistance for new SCPs, jobs, or in-game text.

This keeps the Team’s work practical, staff-aligned, and beneficial to all creative branches.

---

3. Workflow and Day-to-Day Operations
The Team follows a simple, structured workflow:

• Request Phase: Departments submit writing requests (e.g. “Event briefing,” “Lore update”). Logged via Discord or Sheets.
• Assignment Phase: Senior Writers assign tasks with flexible timeframes.
• Drafting Phase: Work is written collaboratively in Docs or Notion using a shared style guide.
• Review & Approval Phase: Senior Writers review tone, consistency, and quality before Event Lead approval.
• Archive Phase: Finalized work is stored in a Lore & Event Archive for future reference and continuity.

---

4. Integration with Civil Networks Systems

CN Division​	Team Interaction​
Event Team​	Provides pre-written event scripts, dialogue, and lore context.​
Content Team​	Assists with lore and text for new SCPs and features.​
Resources Team​	Rewrites and maintains department documentation.​
Server Leadership​	Reviews only major lore additions or canon changes.​

The Narrative Team acts as a creative support branch that improves efficiency and maintains consistency.

---

5. Tools and Standards
To stay efficient, the Team uses:

• Google Drive for writing projects.
• Tracker Sheet for monitoring deadlines.
• Lore Style Guide for formatting and tone.
• Dedicated Discord channels for coordination.

---

6. Application Process
Membership is open to staff and trusted community members:

• Applicants submit a short writing sample (SCP entry, log, or RP doc).
• Accepted applicants begin as Junior Writers with promotion based on quality and reliability.
• Event Leads or Server Leadership can approve exceptional candidates directly.

This ensures inclusivity while maintaining high standards.

---

7. Original Worldbuilding and Creative Expansion
A major goal of the Narrative Team is to establish a unique CN-exclusive canon that develops independently from the SCP Wiki.
While the SCP universe remains an inspiration, Civil Networks has its own evolving story, departments, politics, and events unique to its servers.
The Team collaborates with Event and Content Teams to build this shared world, ensuring all storylines connect into one cohesive, original universe.
This independence fosters creativity, immersion, and identity, giving CN full control over its storytelling direction while respecting its roots.

---

Possible Positives of the Suggestion:

• Improves event quality by freeing hosts to focus on execution.
• Preserves lore consistency across both servers.
• Reduces workload for Content and Resources Teams.
• Encourages creativity through structured collaboration.
• Raises professionalism in documentation and event writing.

---

Possible Negatives of the Suggestion:

• Adds a short review step that could slow approvals.
• Relies on consistent writer participation.
• Requires clear coordination with Event Leads.

---

Based on the Positives & Negatives, why should this suggestion be accepted:
The Narrative Team would provide Civil Networks with a lasting creative framework connecting Event, Content, and Resources Teams.
By ensuring every story fits within a unified canon, CN enhances immersion, professionalism, and long-term narrative continuity.
This small addition offers a major impact on quality, efficiency, and creativity across both SCP-RP servers.

---

"Quality writing builds quality roleplay."​

​

 

[Henrii]

Not relevant to the suggestion:
I highly recommend changing the font to default and use contrasting font colors to the background for readability
And while center alignment is more "organized," it isnt necessarily better honestly

 

[Sleepino]

+support
interesting idea

 

[Aphex]

I'm confused as to how this can't just be done by event team. I'm not sure why it's not done right now, I can imagine it's because a lot of GMs to events with no prior approval or regard for server lore backlash (sometimes without logging it), so I get where this is coming from. I know I've wanted to be more involved with server lore as a whole, but the way the event team is structured and operated right now, making a narrative before an info-reset for both servers is a challenge.

I'd like an overarching narrative for the server that is maintained by a handful of people, but I also like the current structure of spontanious events where people get a good idea, and committ to it early on for a singular, short event.

• Content Team requests lore assistance for new SCPs, jobs, or in-game text.

From what I recall from my time in Content Team, we just made our own lore for new content. SCP-8837 and 8854 are amazing...ly bad examples since 8837 has shit lore (the official ingame document is horrible), and 8854... doesn't have lore.

• Adds a short review step that could slow approvals.
• Relies on consistent writer participation.
• Requires clear coordination with Event Leads.

There has to be more negatives.
I feel like GM could be restricted on what types of events they can do that they previously could depending on the narrative that's being presented. It would also require not only just coordination with Event Leads, but also the entirety of the Event Team as a whole. I have mixed thoughts on event storylines requiring approval.
On the one hand, explaining everything in detail for approval is one thing, but on the other,

actually performing an event or storyline in completely different. You have a picture in your head for the ideal outcome(s) for an event or storyline, but it's very likely it would stray from the intended direction that a narrative team would want to committ to.
Another problem that could be addressed is of normal player agency. Lets imagine a major event occurs that could change the course of a narrative forever. The writers expect 1 or 2 different outcomes, but in reality there are WAY more than what the writers expect. There are ways to solve this issue, like just not deciding on an outcome beforehand and determening afterwards, but that takes a lot more time and effort than the previous method.

7. Original Worldbuilding and Creative Expansion
A major goal of the Narrative Team is to establish a unique CN-exclusive canon that develops independently from the SCP Wiki.
While the SCP universe remains an inspiration, Civil Networks has its own evolving story, departments, politics, and events unique to its servers.
The Team collaborates with Event and Content Teams to build this shared world, ensuring all storylines connect into one cohesive, original universe.
This independence fosters creativity, immersion, and identity, giving CN full control over its storytelling direction while respecting its roots.
​

Technically speaking, this is already the case, but not with as much quality that one would wish for a server like this.
A couple of examples I could bring up is:

• There was an event or storyline (not sure which, not even sure if it's true but I need to speak with those involved to confirm) that essentially depicted the Black Mesa Incident happening within the server world, but it was thwarted by the SCP Foundation (and GOC?).
• ISD as depicted within the SCP Wiki is more akin to the KGB, but on the server it's a mix of Internal Affairs, Human Resources, and also ISD at the same time. Not sure why this is the case, but it is.
• There have been numerous examples of RSD, CI R&D and PTOLEMY projects going through and creating their own little plotlines, I have one on the top of my head, but I forgot what it was outside of it just being SCP-6820 but under a different name and premiseþ

An issue I have with the goal(s) listed here is that it states "A major goal of the Narrative Team is to establish a unique CN-exclusive canon that develops independently from the SCP Wiki."
I don't know if a lot of the community knows this, but the SCP Wiki isn't always consistent.
There are at least like 4 different articles on how Akiva Radiation works, what Humes are, what are the effects of Amnestics on the human mind, etc, that all depict seperate results and outcomes.
So, if a GM wants to use Akiva Radiation for an event, but they they ask the Narrative Team which version or depiction to use, and the Narrative Team haven't read anything about it, they either read through all of the sources and decide on one, or they create their own depiction. Why can't Event Team on their own do this?

If it isn't clear, my thoughts on this entire subject is mixed. I like the idea, but why can't the Event Team just do this on their own? Why does an entirely seperate staff team need to be implemented to facilitate a more cohesive narrative, instead of just using the pre-existing GM team that are fully willing to collaborate to create a wider, more overarching narrative? With the recent addition of Head Game Master, this should be even easier as well since a singular HGM can get a better grasp of what the narrative could possibly become.

 

[Emilia Foddg]

The famously infinitely staffed Civil Networks Staff team, which can reasonably sprout and sustain many teams for every little possible niche.

Additionally, having an entire team oversee things like story and plot typically hampers creativity rather then fostering it. A lot of this just doesn't really make sense and overall seems like bloat that would have more of a emphatic negative impact rather than a positive one, on both the staff teams and server environments.
-Support

 

[Runic]

W idea if the staff team wasnt hemorrhaging for new people 24/7

 

[Michael Dzhetnikov]

+Support*

This seems like it would require a lotta people, it should probably be kept to allowing players to submit applications?

Yap Section
Like the others are saying, this would def clash with the event team's ideas and limit their creativity, but I do agree that we need a few things established, like, why do we refer to reality benders with GOC designation? Why do we have so many Hostile Euclids & Keters onsite? Why do we have both Ethics and Overseer offices on the same site? Could this all be linked to an alternate timeline in which the foundation has less resources? Why are there 4 MTF's onsite? Are they here because of the constant breaches, raids and visits by CL5 personnel? Are they special stationary branches? Why don't we state that they are? Does security clearance correspond to knowledge clearance? Will we ever establish or update the doors that lead to nowhere?

If this doesn't get in this would at least be a good idea in Site-9, as I have a feeling that server lore would very much have a larger impact on the forbidden element: "ROLEPLAY"

 

[Dusk]

I'm confused as to how this can't just be done by event team. I'm not sure why it's not done right now, I can imagine it's because a lot of GMs to events with no prior approval or regard for server lore backlash (sometimes without logging it), so I get where this is coming from. I know I've wanted to be more involved with server lore as a whole, but the way the event team is structured and operated right now, making a narrative before an info-reset for both servers is a challenge.

I'd like an overarching narrative for the server that is maintained by a handful of people, but I also like the current structure of spontanious events where people get a good idea, and committ to it early on for a singular, short event.

From what I recall from my time in Content Team, we just made our own lore for new content. SCP-8837 and 8854 are amazing...ly bad examples since 8837 has shit lore (the official ingame document is horrible), and 8854... doesn't have lore.

There has to be more negatives.
I feel like GM could be restricted on what types of events they can do that they previously could depending on the narrative that's being presented. It would also require not only just coordination with Event Leads, but also the entirety of the Event Team as a whole. I have mixed thoughts on event storylines requiring approval.
On the one hand, explaining everything in detail for approval is one thing, but on the other,

actually performing an event or storyline in completely different. You have a picture in your head for the ideal outcome(s) for an event or storyline, but it's very likely it would stray from the intended direction that a narrative team would want to committ to.
Another problem that could be addressed is of normal player agency. Lets imagine a major event occurs that could change the course of a narrative forever. The writers expect 1 or 2 different outcomes, but in reality there are WAY more than what the writers expect. There are ways to solve this issue, like just not deciding on an outcome beforehand and determening afterwards, but that takes a lot more time and effort than the previous method.

Technically speaking, this is already the case, but not with as much quality that one would wish for a server like this.
A couple of examples I could bring up is:

• There was an event or storyline (not sure which, not even sure if it's true but I need to speak with those involved to confirm) that essentially depicted the Black Mesa Incident happening within the server world, but it was thwarted by the SCP Foundation (and GOC?).
• ISD as depicted within the SCP Wiki is more akin to the KGB, but on the server it's a mix of Internal Affairs, Human Resources, and also ISD at the same time. Not sure why this is the case, but it is.
• There have been numerous examples of RSD, CI R&D and PTOLEMY projects going through and creating their own little plotlines, I have one on the top of my head, but I forgot what it was outside of it just being SCP-6820 but under a different name and premiseþ

An issue I have with the goal(s) listed here is that it states "A major goal of the Narrative Team is to establish a unique CN-exclusive canon that develops independently from the SCP Wiki."
I don't know if a lot of the community knows this, but the SCP Wiki isn't always consistent.
There are at least like 4 different articles on how Akiva Radiation works, what Humes are, what are the effects of Amnestics on the human mind, etc, that all depict seperate results and outcomes.
So, if a GM wants to use Akiva Radiation for an event, but they they ask the Narrative Team which version or depiction to use, and the Narrative Team haven't read anything about it, they either read through all of the sources and decide on one, or they create their own depiction. Why can't Event Team on their own do this?

If it isn't clear, my thoughts on this entire subject is mixed. I like the idea, but why can't the Event Team just do this on their own? Why does an entirely seperate staff team need to be implemented to facilitate a more cohesive narrative, instead of just using the pre-existing GM team that are fully willing to collaborate to create a wider, more overarching narrative? With the recent addition of Head Game Master, this should be even easier as well since a singular HGM can get a better grasp of what the narrative could possibly become.

Fantastic reply! I'll do my best to break this down into some answers, some may be on here, some I may have taken out myself to answer for others that may have similar concerns.

Why can’t the Event Team just handle lore and narrative coordination themselves?

They can for smaller events, and likely always will. The Narrative Team is meant to help with long-term continuity, keeping a clear record of ongoing storylines, outcomes, and references so nothing gets lost between hosts or servers. It takes workload off the Event Team so they can focus on planning and execution instead of documentation.

What responsibilities or tools would the Narrative Team have that the Event Team doesn’t already?

A few simple ones: a shared archive for event outcomes, a basic lore reference guide, and optional writing support for event briefings or documents. Nothing replaces Event Team functions, it just adds resources that make their jobs easier.

Is a new team necessary, or would restructuring the Event Team be a better solution?

This proposal treats the Narrative Team as a sub-team under Event Team, not a new department. It’s a focused branch for writing and record-keeping that stays within the existing structure.

How can spontaneity in events be preserved while maintaining narrative consistency?

By keeping only major lore-affecting events tracked. Normal or spontaneous events don’t need pre-approval, they’re just logged afterward so the story stays consistent without slowing things down.

Would requiring prior event approvals stifle creativity or reduce the number of events?

No, smaller events wouldn’t need approvals at all. The Narrative Team would only step in when a storyline affects global lore or other departments.

How do we handle events that deviate from the original plan due to player behavior?

Event results should always reflect player actions. The Narrative Team simply records the new outcome so the next event can reference what actually happened, keeping things authentic.

Would GMs be restricted in the themes or plots they can explore due to narrative rules?

No. The Team doesn’t write rules, it provides context. As long as themes fit within CN’s tone and common-sense lore, GMs can explore what they want.

How much power should the Narrative Team have, advisory or veto?

Advisory. Any veto power would stay with Event Leads or higher staff. The Team gives input, not authority.

Should major lore-changing events be handled differently from small-scale ones?

Yes. Big events that change canon would be reviewed first so everything aligns with ongoing arcs, while smaller events can be logged after they run.

Why isn’t coordination with Content and Event Teams enough?

Coordination works in the short term, but written lore and outcomes often get lost over time. The Narrative Team ensures that information stays recorded and easy to find later.

Should the Narrative Team be a sub-team of Event Team or standalone?

Sub-team. It doesn’t need its own hierarchy, it operates under Event Team leadership using shared tools and communication channels.

What role should the Head Game Master play in narrative cohesion?

Oversight and connection. They’d approve or schedule large story arcs and help ensure events don’t overlap or contradict each other.

What is CN’s stance on inconsistencies in SCP Wiki canon (e.g., Akiva Radiation)?

Civil Networks already treats SCP Wiki canon as flexible. If something doesn’t fit gameplay or tone, CN lore takes priority.

Should CN server canon replace, remix, or align with SCP Wiki canon?

Remix and align where practical. CN’s goal is to build its own version of the SCP universe, familiar but unique to its servers.

How should the Narrative Team account for player agency altering event outcomes?

Player choices define the story. The Team would only log those outcomes afterward and help adjust follow-up events accordingly.

Should outcomes be pre-planned or reactive based on how events unfold?

Reactive. Event plans can have optional outcomes, but what happens in-game should always take priority.

Is this solving a real issue, or just patching a lack of coordination/documentation?

It’s addressing both. Many events and documents are lost or forgotten. This provides a simple way to keep CN’s stories connected without overhauling anything.

What safeguards would prevent the Narrative Team from becoming a bottleneck?

It has no approval authority. It’s optional support, GMs can request help, but aren’t forced to wait for it. That alone prevents bottlenecks.

Would this system actually prevent bad lore from being added?

Not entirely, but it helps. Having peer review and consistent documentation reduces the chances of rushed or contradictory lore being added.

How will success of the Narrative Team be measured?

By player feedback, event clarity, and how often past stories are referenced or built on. If events connect naturally and lore feels coherent, it’s working.

 

[Dusk]

The famously infinitely staffed Civil Networks Staff team, which can reasonably sprout and sustain many teams for every little possible niche.

Additionally, having an entire team oversee things like story and plot typically hampers creativity rather then fostering it. A lot of this just doesn't really make sense and overall seems like bloat that would have more of a emphatic negative impact rather than a positive one, on both the staff teams and server environments.
-Support

Not to stifle anyone’s creativity, but Civil Networks doesn’t really have an overarching story, and that’s both its strength and its limitation. The best moments on the server come from originality, but half of that creativity relies on proper organization and documentation, which have always been the weakest points for long-term development.

If CN wants to move forward, its originality needs to come from its own server history, not from repeating familiar concepts like Resh-1 introductions or command promotions. There have been some incredible events, but they often disappear as quickly as the players who created them.

For me, the true weight of a story doesn’t come from the action itself, but from the history built around it. The issue isn’t a lack of ideas, it’s that the staff and event structure aren’t currently equipped to build or maintain a long-term narrative. That’s why we see isolated bursts of creativity instead of a continuing story that defines the world.

+Support*

This seems like it would require a lotta people, it should probably be kept to allowing players to submit applications?

Yap Section
Like the others are saying, this would def clash with the event team's ideas and limit their creativity, but I do agree that we need a few things established, like, why do we refer to reality benders with GOC designation? Why do we have so many Hostile Euclids & Keters onsite? Why do we have both Ethics and Overseer offices on the same site? Could this all be linked to an alternate timeline in which the foundation has less resources? Why are there 4 MTF's onsite? Are they here because of the constant breaches, raids and visits by CL5 personnel? Are they special stationary branches? Why don't we state that they are? Does security clearance correspond to knowledge clearance? Will we ever establish or update the doors that lead to nowhere?

If this doesn't get in this would at least be a good idea in Site-9, as I have a feeling that server lore would very much have a larger impact on the forbidden element: "ROLEPLAY"

That’s exactly the kind of discussion the Narrative Team is meant to encourage, not restrict.
Right now, questions like the ones you brought up get asked all the time, but they rarely get clear answers because there’s no consistent documentation or system to track them. The point isn’t to force every event or story into a single direction, but to create a central space where this type of worldbuilding can be recorded, referenced, and expanded on later.

If we had an active record or internal wiki that addressed things like:

• Why reality benders are tagged under GOC classifications,
• Why Site-65 has multiple MTF detachments and CL5 visitors,
• Or how Ethics and O5 divisions coexist on the same site,

then GMs and staff would have creative freedom with context, they could reference, rewrite, or challenge that established lore without contradicting themselves or others.

The Narrative Team isn’t about limiting creativity; it’s about giving it structure to last beyond a single event. It’s the difference between one great story and a world that remembers it.



*EDIT for further clarification and impact.

1. Ease of Access
Right now, lore exists in fragments, scattered across old documents, event logs, and player memories. A centralized canon would give everyone, from new players to senior staff, a single place to understand how the server’s universe operates. It eliminates confusion about what is or isn’t considered canon and gives players a consistent point of reference for events, departments, and roles.

2. Character Weight and Identity
A defined lore framework gives characters meaning beyond their current play sessions. Instead of being just another name on a job, players can have characters who are recognized as part of Civil Networks’ history. This creates a sense of legacy and progression where actions, discoveries, and leadership leave a visible mark on the server’s story.

3. Stronger, More Meaningful Stories
Without a shared canon, most events tend to start and end without lasting impact. By connecting them through a central narrative, each story builds on the last, creating cause and effect that makes the world feel alive. It gives players reasons to care about outcomes because their choices influence what happens next.

4. Preservation and Future Use
Having organized, written material means ideas and stories don’t fade when the players or staff behind them move on. It allows future event hosts or departments to reuse established lore, locations, and characters instead of starting from scratch each time. This builds continuity and saves time while maintaining quality.

5. Building a Lasting History for Civil Networks
The goal isn’t to replace creativity, but to give it a foundation. When the server has its own evolving history, it becomes more than a collection of disconnected moments, it becomes a living timeline. That timeline can be referenced, expanded, and remembered, giving Civil Networks its own unique identity separate from the SCP Wiki or other communities.

 

[Emilia Foddg]

Not to stifle anyone’s creativity, but Civil Networks doesn’t really have an overarching story, and that’s both its strength and its limitation. The best moments on the server come from originality, but half of that creativity relies on proper organization and documentation, which have always been the weakest points for long-term development.

If CN wants to move forward, its originality needs to come from its own server history, not from repeating familiar concepts like Resh-1 introductions or command promotions. There have been some incredible events, but they often disappear as quickly as the players who created them.

For me, the true weight of a story doesn’t come from the action itself, but from the history built around it. The issue isn’t a lack of ideas, it’s that the staff and event structure aren’t currently equipped to build or maintain a long-term narrative. That’s why we see isolated bursts of creativity instead of a continuing story that defines the world.

Yes - This is the natural outcome of the kind of community that CN is, sporadic bursts of fun, creative storytelling & gameplay that are a byproduct of the fact that this is intrinsically an amorphous place; People can show up and if they're interested, start contributing their own ideas and such to the shared world of sorts. And on the other side of that, people can depart at any time for any reason.

The reason why we see isolated bursts of creativity instead of a continuing and defining story is because the overall makeup of the community changes on the fly. Establishing a (sub)team to try and maintain a long-term narrative is not feasibly sustainable for this reason. Everything is in flux and that's really the way things should be. I know that your idea isn't strictly antithetical to the current flexibility of how this works on the server right now, but I see this encouraging and fostering the wrong things.

 

[Dusk]

Yes - This is the natural outcome of the kind of community that CN is, sporadic bursts of fun, creative storytelling & gameplay that are a byproduct of the fact that this is intrinsically an amorphous place; People can show up and if they're interested, start contributing their own ideas and such to the shared world of sorts. And on the other side of that, people can depart at any time for any reason.

The reason why we see isolated bursts of creativity instead of a continuing and defining story is because the overall makeup of the community changes on the fly. Establishing a (sub)team to try and maintain a long-term narrative is not feasibly sustainable for this reason. Everything is in flux and that's really the way things should be. I know that your idea isn't strictly antithetical to the current flexibility of how this works on the server right now, but I see this encouraging and fostering the wrong things.

It’s strange to me to see the idea of organization or consistency framed as something that would somehow harm creativity. The truth is, disorganization doesn’t encourage creativity, it isolates it. When every player or staff member tells their own disconnected story, none of it carries weight, because nothing exists beyond the moment. That’s not creative freedom, that’s just noise.

You’re telling me that isolated bursts of content with no continuity somehow carry more weight than an overarching storyline where everything, from events to characters to even PAC3 creations, can be connected and framed with meaning? Civil Networks was built on creative expression, but creativity without context fades fast. A one off event might be fun in the moment, but it doesn’t contribute to the bigger picture of what the server is or where it’s going. The reason players lose interest after major events isn’t because they don’t enjoy them, it’s because those moments end without consequence, no follow-up, no reference, no history.

A connected narrative doesn’t erase spontaneity; it enhances it. It gives those isolated ideas a place to live, breathe, and grow into something greater. Every action, character, and creation could hold long term meaning because it ties into something shared. If we’re a community built on creativity, then we should be protecting that creativity, not letting it vanish because no one wrote it down or tied it to something bigger.