Employees are encouraged to set their login passwords using inspiration from the Approved Corporate Affirmations.
— Section 4.3.2, Digital Conduct Protocols
Welcome to BlogNomic, a self-modifying game where changing the rules is a move. Players make blog posts proposing alterations to the ruleset, discussing and casting votes in the comments: if enough vote in favour, the rules are changed and play continues.
The game has been running since 2003 and resets every month or so. Have a look around the wiki for more information and history, or join our Discord. New players are always welcome to join the game at any time.
Friday, September 05, 2025
Employee Handbook Quote of the Day (0 comments) Employees are encouraged to set their login passwords using inspiration from th
Wednesday, September 10, 2025
Call for Judgment: Redaction Window Closure
Remove the text “A BLANK cannot be closed until 96 hours have passed since it was posted.” from the rule “Redaction”
There are currently two conflicting statements about when a BLANK can be closed.
“A BLANK cannot be closed until 96 hours have passed since it was posted.”
“Once a BLANK has been open for at least 72 hours, the BOARD may close the BLANK.”
I could see different interpretations here for which one to uphold. It’s clear that the Redaction mini-game needs to be reworked, but until it then it seems more reasonable to delay 72 hours than 96 hours given the high difficulty of the task currently.
Proposal: I don’t think they exist
For each Innie who is assigned to the Redacted Department, randomly select one of the other Departments, and reassign that Innie from the Redacted Department to the Department so selected.
Story Post: Report: Lawnomos
In their report against me, Lawnomos called out my vote on Branch Transfer System as being “incentiviz[ing] sabotaging [my] department”.
The Board has also voted in favour of the same proposal.
The insult against me is therefore also an insult against the Board. I suggest that they be reprimanded for this lack of esprit de corps.
BLANK - September 10
__pp_
_ng___
_oz_
_a__i____
sh_____
____ba__
___dp__
_ri__
_br_____
c_______r
Story Post: Correlation Day
A Correlation Tally has been been performed. The Index Correlation Department has reduced its Quota by 3. Glory to the Board.
Story Post: Report: Josh
Josh has refused to increase his Work Ethic and help his Department over 12 times when he was doing Blognomic. He has also voted for a proposal that incentivized sabotaging your department so you could be transferred out of it.
The Workplace Code gives clear guidelines that “Innies should not take any action to harm their own department”. In this case, the “actions” in particular were “making a choice not to increase their Work Ethic, even when it could have singlehandedly improved their Department’s Departmental Effort”.
Furthermore, he has proposed to directly punish another player and his department (while these do not break the Workplace Code). I believe he should be warned and reprimanded, which is why I am submitting this report. I await the Board’s Decision.
Proposal: Your zeal is better placed elsewhere
Move the Innie SingularByte to the Redacted department.
We want you to ████ ██████████ ███ ██ ████████
Signing Off
I idle. Quorum drops to 6.
Large dynasty keeping up issue, schoolwork and other stressors and timing stuff not helping.
Voluntary Severance Package
I would like to idle, please.
Having trouble keeping up with a large dynasty.
Wednesday, September 10, 2025
Proposal: Power Up Research, 1
Replace the following text “ If each of the Innies in the Department of Redacted have posted a valid Guess to the BLANK, reduce the quota of the Department of Redacted by 1, to a minimum of 0.” with
For each of the Innies in the Department of Redacted have posted a valid Guess to the BLANK, reduce the quota of the Department of Redacted by 1, to a minimum of 0.
Replace the following text ” Replace all but 2 letters in each of the 10 words with underscores.” with
Replace all but 3 letters in each of the 10 words with underscores.
Delete the following text ‘A BLANK cannot be closed until 96 hours have passed since it was posted”.
Replace the following text “Once a BLANK has been open for at least 72 hours” with
Once a BLANK has been open for at least 48 hours
Append the following in the rule Redacted:
The Board may create a BLANK at their earliest convenience, and may not take any other Dynastic Action other than creating a BLANK or closing the BLANK if there is currently not a Open BLANK or the current Open BLANK is open for more than 48 hours.
Proposal: Metabalancing
Add a new Rule, named Metabalancing with the following text:
For any Department who is not Temporal Assurance, if they fulfill any Quotas they instead fulfill double the amount of Quotas.
Intending this to be a short term balancing effort against Temporal Assurance, as SingularByte saying that it is our duty to fix up our Quota-making.
Proposal: All Work, No Play
In the rule “Performance Cycles”, if there is the text “When one or more Departments’ Quota has been 0 for at least 24 hours, the current Performance Cycle ends.” replace it with:
When one or more Departments’ Quota reaches 0, the current Performance Cycle ends.
Within the rule “Performance Cycles”, after the step known as “Improvement Needed”, if there is no step starting with “Personal Improvement Plan” insert the following step:
Personal Improvement Plan: For each Innie with one or more Reprimands, increase the Stress of that Innie by their number of Reprimands.
In the rule “Performance Cycles”, replace the Quota Evaluation step with:
Quota Evaluation: For each Department, determine whether it has Met or Failed its Quota for this Performance Cycle. Where a department has a Project with its Progress equal to or greater than a goal, then for each such project, that department’s quota is considered to be one lower than its current value (to a minumum of 0).
This is intended to be a proposal competing against Gift Basket. Rather than having people wait 24 hours, this one simply treats the projects pending completion as if they were actually completed. It retains the reprimands change so that if this passes, it doesn’t matter whether Gift Basked passed or failed.
Proposal: Sounding smart
Create a subrule of Departments called Lexical Adjustment:
As a daily action, the Board should set a new Word of the Day, which may be any English word of three or more syllables. The current Word of the Day is publicly tracked, and defaults to Abacus.
As a daily action, an Innie in the department of Lexical Adjustment may decrease the quota of their department by 1 so long as they have used the Word of the Day correctly in an Official Post, or as a comment of an Official Post, within the last hour. To have used it correctly, it must be part of a valid sentence and must not simply a sentence commenting on the word itself (e.g. a comment of “Abacus has 6 letters” would not be valid), though it is not required to fit in the context of the other sentences of the post or comment.
Proposal: Cures For Amnesia 101
If there is no rule “Memories”, create it.
Reword the rule “Memories” to the following:
There is a publicly tracked list of Memories, defaulting to blank. Each Memory has a publicly tracked ID which can be any Integer not already held by a Memory, and a publicly tracked Owner, which can be any Innie or blank (default), a publicly tracked flavor text Fragment, which may be a text string or blank (default), and a publicly tracked flavor text Context, which is a statement about that Memory’s Owner that can be true or false in the current gamestate and which is, by default, “This Memory’s Owner is an Innie”. An Innie’s Memory is Active when its Context is true and Suppressed when its Context is not true.
As a Weekly Action, an Innie may Train Memory. When an Innie Trains Memory, he creates a new memory with him as the Owner, and randomly chooses a context from the below list, and applies any instructions in brackets associated with that
Context:
*This Memory’s Owner Owns a X (then roll {Finger Trap, Specialized Algorithms} and replace X with the result)
*This Memory’s Owner Has a Stress of X (then roll a DICE5 and subtract 1, replacing X with the adjusted result)
*This Memory’s Owner Has a Reprimands of X (then roll a DICE7 and subtract 1, replacing X with the adjusted result)
*This Memory’s Owner’s Department has a Quota of 0
*This Memory’s Owner has posted a Report and there is no Voting Icons in the Board’s Comments on it.As a Daily Action, any Innie or the Board may change the Context of any Active Memory to “This Memory’s Owner is a Innie.”
As a Daily Action the Board may choose the Active Memory with a Fragment of Blank, and the Smallest ID, and then the Board randomly chooses a line from this list and follow the instructions.:
*Use the random name generator at https://www.behindthename.com/random/ to randomly select a name (the Board may change the settings on the Random Name Generator before doing so), and then set the selected Memory’s Fragment to “Your Name is N”, where N is the generated name.
This fleshes out Memories so you can play the minigame (though it has no effect yet). Basically, you try to activate a trigger and once that trigger is completed, you remember something.
Proposal: Branch Transfer System
In the rule “Departments”, add the following text as a new paragraph:
A Department’s Team Performance equals the mean Evaluation Point of all Innies in that Department.
In the rule “Performance Cycles”, in the steps for Performance Review, before the step that starts with the text “New Cycle”, add the following steps:
* Branch Transfer: Perform the following substeps
** Cream of the Crop: From the Department with the highest Team Performance, publicly randomly selecting from any ties, select the Innie in that Department with the highest Evaluation Point as the Top Performer, publicly randomly selecting from any ties.
** Last Chances: From the Department with the lowest Team Performance, publicly randomly selecting from any ties, select the Innie in that Department with the lowest Evaluation Point as the Bottom Performer, publicly randomly selecting from any ties.
** Harmonizing the Team Equilibrium: If there is any Department with fewer Innies than any other Department, assign the Top Performer to that Department if they aren’t already assigned to that Department.
** Balancing the Humours: If the Top Performer did not change Departments in the previous step, swap the assigned Departments of the Top Performer and the Bottom Performer.
Balancing Departments every Performance Cycle, first by number and then by performance if the numbers are roughly even.
Proposal: This Conversation will be Recorded for Quality Assurance and Training
If “Stapler in Jello” was not enacted, the rest of this Proposal has no effect.
In the rule “The Water Cooler”, after the text “as if the rule No Private Communications was not in effect” add the following text:
, provided that all of the following criteria are satisfied during such communications:
* All Innies in that Department, as well as The Board, must be included in each communication (e.g. Discord DM group or blog message receipients).
* If an Innie is removed from or added to that Department, any communication group used by any Innies from that Department prior to that point must no longer be used (e.g. prior Discord DM groups or blog message threads).
Using the ideas from the comments in “Stapler in Jello”
Proposal: Worry About Him
Repeal the rule “Outies” and repeal the rule “Memories” as well.
Phrased like this because I do my utmost to avoid the issue of placing punctuation inside or outside quotation marks.
Proposal: Overtime
In the rule “Departments”, replace the text “Add DICE47 hours to the current time” with the text “Add DICE47+48 hours to the current time”.
Clearing 6+ Quota in less than 12 hours is too much of an advantage, in my opinion.
Proposal: No Ex Post Facto
If https://blognomic.com/archive/gybuzvkmo_bevoc was enacted, add the following to “Workplace Code of Conduct”
For determining if an action violated the workplace code, the part of the workplace code being violated must have been part of the workplace code when the action occurred.
otherwise, add the following to “Workplace Code of Conduct”
For determining if an action violated the workplace rules, the part of the workplace rules being violated must have been part of the workplace rules when the action occurred.
Josh pointed out a problem with the existing rules that should probably be fixed
Proposal: Gift Basket
Within the rule “Projects”, replace the text
At any time, a Innie in a Department with a Project assigned to them which has Progress equal to or more than the Goal may remove the project, apply the Project Reward, and decrement the Department’s Quota by 1. Then, if they have no Project assigned to them, add a new Project to the list and assign the created Project to their Department.
with the text
If at any time a Department with a Project has Progress equal to or more than the Goal, any Innie (or the Board) may remove the project, apply the Project Reward to the Innies in said Department, and decrement the Department’s Quota by 1. Then, if the Department has no assigned Project, add a new Project to the list and assign the created Project to the aforementioned Department.
Within the rule “Performance Cycles”, replace the text
When one or more Departments’ Quota reaches 0, the current Performance Cycle ends.
with the text
When one or more Departments’ Quota has been 0 for at least 24 hours, the current Performance Cycle ends.
Within the rule “Performance Cycles”, after the step known as “Improvement Needed”, insert the following step:
Personal Improvement Plan: For each Innie with one or more Reprimands, increase the Stress of that Innie by their number of Reprimands.
- Any Innie (or the Board) should be able to process the completion of a Project, not just the Innies in the Department that completed the Project.
- Projects can be completed at the same time, but are processed separately. This introduces timing scams wherein two Departments can finish their 10th Project at the same time, but if one Department process the removal first, the other Department is punished for not “meeting Quota”, despite having completed all 10 projects. The addition of the 24 hour timer once a Department’s Quota is completed will help ensure this is not an issue.
- There is no current punishment associated with Reprimands. This adds an increase in Stress based on the number of Reprimands an Innie has received.
Clocking out
Lately I’ve found myself in a bit of a rough patch mentally and need a break to reboot if you will. As such, I would like to be idled.
Story Post: Let this be your Motivation
The Board seeks a mechanism by which the exceptional performance of one Department may serve as an energizing influence upon the others. Specifically, this Bounty Notice requests a ruleset change that causes the quota-completing success of one Department to result in a measurable increase in Stress for Innies assigned to Departments that have not yet met their Quota.
After all, stress is not failure. Stress is focus. Stress is fuel. Let this success be contagious.
Bounty Payout: Two Finger Traps will be awarded to any Innie who authors an enacted Votable Matter that clearly satisfies this request.
Proposal: Stapler in Jello
Add a new subrule to the rule Departments, called The Water Cooler:
Innies who are part of the same Department as each other may communicate as if the rule No Private Communications was not in effect.
Proposal: Don’t Worry About Him
Repeal the rule “Outies”.
Repeal the rule “Loss”.
Per the comments on Quarterly Performance Check. Repealing Outies because the game goals has shifted away from uprising-ish stuff (though through Code of Conduct and Memories there’s still some room to explore that) to more “work for the board” stuff. Loss goes because it’s the shortest and still had some opposition around the name unfairness issue.
Monday, September 08, 2025
Retirement Party for arthexis
arthexis has been made idle due to having no posts, comments, or votes on the blog in the past 7 days. Quorum remains unchanged at 8.
Proposal: Gybuzvkmo Bevoc
Popular, 9-0. Enacted by JonathanDark.
Adminned at 09 Sep 2025 21:41:26 UTC
Reword the text “There exists a number of Workplace Rules that all Innies are expected to follow. These rules are not binding, though breaking them may still face dynastic consequences.” in the rule “Workplace Code of Conduct” to read:
There exists a number of Workplace Codes. An Innie who fails to obey any of the Workplace Codes during this Dynasty may expect to be reprimanded by the Board.
Replace all instances of the text Workplace Rule in the Dynastic Rules with Workplace Code.
I don’t like overloading the word “rule,” and this also addresses Josh’s point about the span of relevant time.
Proposal: U_der_c_re
Popular, 8-0 with 1 DEF and Board voting FOR. Enacted by JonathanDark.
Adminned at 09 Sep 2025 21:38:36 UTC
In the rule “Departments” add a subrule called “Redaction” with the following text:
There exists a BLANK, which is a Story Post - Votable Matter. Only the Board may create a BLANK. Creating a BLANK is an atomic action consisting of the following steps:
*Privately randomly choose 10 words from the EFF Wordlist. These are known as the Original Words.
*Replace all but 2 letters in each of the 10 words with underscores.
*Post the modified list of words to the blog as a Story Post - Votable Matter, with the title “BLANK - Day”, with “Day” being replaced with the current date.
A BLANK cannot be closed until 96 hours have passed since it was posted. A BLANK can only be closed by the BOARD. A new BLANK cannot be posted if there is currently an open BLANK. While a BLANK is open, all Innies in the Department of Redacted may post a Guess to the BLANK, which is a comment consisting of 10 words that they believe to be the Original Words. If an Innie posts more than one Guess to a BLANK, only that Innie’s most recent Guess is counted as their Guess.
Once a BLANK has been open for at least 72 hours, the BOARD may close the BLANK. Closing a BLANK is an atomic action consisting of the following steps:
*Post a comment to the BLANK stating “This BLANK is now closed.”
*If each of the Innies in the Department of Redacted have posted a valid Guess to the BLANK, reduce the quota of the Department of Redacted by 1, to a minimum of 0.
*For each Guess which correctly identifies at least 5 of the Original Words, reduce the quota of the Department of Redacted by 1, to a minimum of 0.
*For each Guess which correctly identifies all 10 of the Original Words, reduce the quota of the Department of Redacted by 1, to a minimum of 0.
Proposal: Burning the Midnight Oil
Popular, 9-0. Enacted by JonathanDark.
Adminned at 09 Sep 2025 21:36:34 UTC
In the rule “Projects”, add a subrule named “Overtime” with the following text:
As a Daily Action, an Innie whose Work Ethic is greater than 1 may choose to Work Overtime, which is an atomic action with the following steps:
* Increase the Progress of one of the Projects assigned to that Innie’s Department by 1.
* Increase that Innie’s Stress by 1, adjusting their Work Ethic accordingly.
Proposal: Providing Guidance to the Board
Popular, 7-0. Enacted by JonathanDark.
Adminned at 09 Sep 2025 21:34:54 UTC
In the rule “Index Correlation”, before the text “an Innie in the Department of Index Correlation can set their Guidance Index” insert the text “as a Virtual Action”.
Right now there’s no indication of how an Innie sets their Guidance Index, since it’s privately tracked by the Board and thus an Innie can’t set it directly.
Call for Judgment: Coreless
Popular, 9-0. Enacted by JonathanDark.
Adminned at 08 Sep 2025 22:36:05 UTC
Uphold the attempted enactment of the Proposal Headstart ( https://blognomic.com/archive/headstart ) by Chiiika between 6:10:00 UTC 8th September 2025 and 6:20:00 UTC 8th September 2025,
Um…. I think Headstart’s missing a [Core] tag. Oops.
Proposal: Needs Of The Business
Popular, 10-0 with 1 DEF and Board voting FOR. Enacted by JonathanDark.
Adminned at 09 Sep 2025 21:29:48 UTC
As a subrule of Projects, add a subrule Special Projects:
There exist Special Projects, which are Projects. All types of Special Project are found in the Special Projects table in this rule. When a Special Project of a given type is created, the Goal and Project Reward are to be taken from the respective columns of the relevant row of the Special Projects table, rather than being the normal Project defaults.
Special Project || Goal || Project Reward
Team Bonding Exercise || 10 || Each Innie in the Department that completed this project loses 1 stress (if possible), and gains 1 Evaluation Point.
Cross-Team Box Ticking Exercise || 5 || Increase the Quota of all Departments, except the Department that completed this project, by 5, and each Innie gains 2 Evaluation Points.
Develop Automation || 10 || Each Innie in the Department that completed this project gets one Specialised Algorithms perk and 2 Evaluation Points.
Flagship Project || 50 || Each Innie in the Department that completed this project gets one Recognition of the Board perk and 20 Evaluation Points.
Add the following Perks to the list of Perks in Perks:
Specialised Algorithm
Description: A floppy disk contains algorithms designed to do one, and only one, task. The ever varying nature of their work ensures it never stays useful for long.
Effect: The innie who holds this perk may at any time reduce either their Department’s quota by 2, or a project’s goal by 2. When this effect is used, the Perk is removed from that Innie.Recognition of the Board
Description: A certificate with a gold stamp on it, recognising an Innie’s great feats.
Effect: The innie who holds this perk is always classed as a star employee, and never a slacker.
Currently there’s no way to get Special Projects, but I figure that can be a later proposal.
Proposal: Right Way Up
Popular, 7-2 with 2 DEFs and Board voting FOR. Enacted by JonathanDark.
Adminned at 09 Sep 2025 21:27:34 UTC
In the rule Index Correlation, replace:
* For each Innie in the Department of Index Correlation that has a non-zero Guidance Index that is at least 2 less than the Performance Index and no greater than 2 more than the Performance Index, reduce the quota of the Department of Index Correlation by 1, to a minimum of 0.
with:
* For each Innie in the Department of Index Correlation that has a non-zero Guidance Index that is between the Performance Index +- 2 (inclusive), reduce the quota of the Department of Index Correlation by 1, to a minimum of 0.
“At least 2 less” can be read in two different ways with essentially opposite meanings. Either you have to have a value which is 2+ lower than the performance index, or you have to have a higher value than (performance index - 2).
Sunday, September 07, 2025
Proposal: Quarterly Performance Review
Timed out, 6-6. Failed by JonathanDark.
Adminned at 09 Sep 2025 20:15:18 UTC
Repeal “Workplace Code of Conduct”.
Repeal “Loss”.
Repeal “Outies”.
Repeal “Memories”.
Remove the bullet point Improvement Needed from Performance Cycles.
Echoing Josh’s point in The Partition Protocol; I think that this proposal bunch out the parts that are making the whole gamestate extremely clunky to work on; I think that a main theme of “employee doing work on projects and getting eval points out of that” is a possible cycle; but that would require more fixes and stuff; especially with how the stress meter and the work effort interact.
Sunday, September 07, 2025
Proposal: Headstart
enacted 8/1, chiiika.
Adminned at 08 Sep 2025 06:16:15 UTC
Reword
Additionally, Proposals may be submitted and resolved as normal, provided that they only have the effect of amending the non-dynastic ruleset and/or the Building Blocks page.
to read
If the game is in an Interregnum and the Board has posted an Ascension Address during this Interregnum, then Proposals may be submitted as if the game was not in Hiatus.
If the game is in an Interregnum, Proposals may be submitted and resolved as if the game was not in Hiatus provided they do not change the Dynastic Rules or Gamestate defined by Dynastic Rules.
A rewrite of https://blognomic.com/archive/imperial_exception to account for the new emperor pronoun and the suggestion to allow all players to propose. You’ll notice this doesn’t allow for such proposals to be resolved, only submitted.
Proposal: The Partition Protocol
wd’d, chiiika.
Adminned at 08 Sep 2025 04:50:35 UTC
Replace the term “Innie” with “Workself” in the Ruleset and the Building Blocks.
Replace the term “Outie” with “Lifeself” in the Ruleset.
Replace any references on blog posts since the most recent Ascension Address to “Lumon” or “Lumon Industries” with “Echelon” or “Echelon Solutions”.
Replace the terms “Innie” and “Outie” with “Workself” and “Lifeself” in the most recent Ascension Address and in any subsequent blog post.
Replace the terms “severance” and “severed” with “partioning” and “partioned” in the most recent Ascension Address.
If the proposal named “Restructuring” has been enacted then replace the following text:
* Finger Trap
- Description: A brightly colored plastic finger trap toy that provides an immediate, if temporary, distraction.
with
* Fidget Spinner
- Description: A white fidget spinner toy that provides an immediate, if temporary, distraction.
Remove the following text from the most recent Ascension Address:
I generally encourage all players to refrain from introducing major spoilers for those who have not seen the show Severance but to simply introduce mechanics and content that is line with the general feel and aesthetics of the show.
This is an effort to separate the dynasty from being related to the show Severance. When I put the Ascension Address together I meant for this to be generic and loosely based on the “severance” concept from the show. But it seems that this has created some confusion for players. I want all players to be able to pick up on the theme simply by reading the Ascension Address without feeling that they may be missing out on additional context or putting pressure on players who have seen the show to include any related elements. I feel this proposal should make it more palatable.
I worry that this was poorly executed and has led to lack of enthusiasm for the current dynasty. I would be equally open to a CfJ that scraps this dynasty and passes the mantle on to another player.
Proposal: Performing Gateway Research
wd’d, chiiika.
Adminned at 08 Sep 2025 04:49:53 UTC
Adds a new subrule under Departments, with the name Redacted with the following text:
The Redacted Department works in brain-control chip research. As a Daily Action, a Innie may perform Research, rolling 5 6 faced dice and select what to keep, then rerolling the unchosen dices and choose what to keep, then reroll the unchosen dice. If at least 4 numbers are the same, the Department named Redacted fulfill 2 Quota. If there are 5 numbers that are the same, instead fulfill 5 Quota.
If ever the Quota of the department named Redacted is 0 and Quota is fulfilled for the Department named Redacted, such fulfillment instead get stored in the Research Effort pool which value is publically tracked.
Saturday, September 06, 2025
Proposal: Turning Correlation Into Causation
timed out 6/1, chiiika.
Adminned at 08 Sep 2025 04:49:24 UTC
In the rule “Departments” add a subrule called “Index Correlation” with the following text:
Each Innie has a Guidance Index, privately tracked by the Board, which is a number that is at least 0 and defaults to 0. If they have not done so since the last Correlation Tally was performed (or since the beginning of the dynasty if a Correlation Tally has never been performed in this dynasty), an Innie in the Department of Index Correlation can set their Guidance Index.
The Performance Index is the mean of all Innies’ Evaluation Point, rounded down to the nearest integer.
Correlation Day is a date privately tracked by the Board that is September 10 2025 by default. If the current date is on or after the Correlation Day 00:00 UTC, at their earliest convenience the Board should perform the Correlation Tally, which is an atomic action with the following steps:
* If at least 50% (rounded down) of the Innies in the Department of Index Correlation have a Guidance Index that is non-zero, reduce the quota of the Department of Index Correlation by 1, to a minimum of 0.
* If all Innies in the Department of Index Correlation have a Guidance Index that is non-zero, reduce the quota of the Department of Index Correlation by 1, to a minimum of 0.
* For each Innie in the Department of Index Correlation that has a non-zero Guidance Index that is at least 2 less than the Performance Index and no greater than 2 more than the Performance Index, reduce the quota of the Department of Index Correlation by 1, to a minimum of 0.
* Set each Innie’s Guidance Index to 0.
* Privately randomly roll DICE3 + 2, and add the result in days to the Correlation Day.
* Make a blog post in the Story Post category indicating that a Correlation Tally has been performed.
The Innies in the Department of Index Correlation should be trying to give guidance to the Board on how they think the employees of the company will perform, correlating their behaviors with their expected performance, in order to meet the department’s quota.
Since the Board is unpredictable, the exact day of the next Correlation Tally is also unpredictable.
Proposal: Synchronise watches, everyone
timed out 7+1/2, chiiika.
Adminned at 08 Sep 2025 04:44:33 UTC
If fewer than three Innies in the Department of Temporal Assurance vote FOR or DEF on this proposal, it has no further effect. Otherwise:
As a subrule of departments, add a subrule Temporal Assurance:
There exists a Pending Temporal Event, which has a publicly tracked date & time, and a publicly tracked status which is either Processed or Unprocessed.
If the Pending Temporal Event is Processed, any Innie in the Department of Temporal Assurance, or the Board, may Run the Numbers.
This is an atomic action with the following steps:
* Set the Pending Temporal Event to Unprocessed.
* Add DICE47 hours to the current time, rounding up to the closest hour, to get a future date and time. Save that as the Pending Temporal Event date and time.
* Change the Pending Temporal Event time’s minutes value to the result of a DICE60.If the Pending Temporal Event is Unprocessed, and is either fewer than 5 minutes in the future or is in the past, any Innie in the Department of Temporal Assurance may Process the Temporal Event. This is an atomic action with the following steps:
* Set the Pending Temporal Event to Processed.
* According to the time that the previous step was completed:
** If the Pending Temporal Event was set to processed within 5 minutes (before or after) the designated time of that Pending Temporal Event, reduce the quota of the Department of Temporal Assurance by 3.
** Otherwise, if the Pending Temporal Event was set to processed within half an hour of the designated time of that Pending Temporal Event, reduce the quota of the Department of Temporal Assurance by 2.
** Otherwise, if the Pending Temporal Event was set to processed within four hours of the designated time of that Pending Temporal Event, reduce the quota of the Department of Temporal Assurance by 1.
** Otherwise the Department of Temporal Assurance does not reduce their quota.
Take the Run the Numbers atomic action.
In addition to projects decreasing the quota, we should also have department-specific means of meeting it. As a member of Temporal Assurance, I’m thinking ours should be time based.
Proposal: Has Anyone Seen My Stapler?
enacted 9+1/1, chiiika.
Adminned at 08 Sep 2025 04:34:21 UTC
Has Anyone Seen My Stapler?
Add a rule named “Shared Workspaces” with the following text:
Each Innie has a Desk Drawer, which is privately tracked by the Board and may be either empty or contain a string of between 5-50 characters that is considered flavour text, defaulting to empty. When not empty, the allowed characters in a Desk Drawer are the 26 letters of the Latin alphabet, numbers, underscores, hyphens, spaces, and full stops. At any time as a Virtual Action, an Innie may set the contents of their Desk Drawer to empty.
As a Daily Virtual Action called a Secret Drop, an Innie may add a string of their choosing, provided that string is legal for the contents of a Desk Drawer, to another Innie’s Desk Drawer, known as the Target Drawer in that instance of that action, provided that Target Drawer has not been part of a Secret Drop action from that Innie in the past 72 hours. If the result of that action would cause the contents of the Target Drawer to be illegal, the action fails.
As a Daily Action known as a Drawer Check, the Board should perform the following steps as an atomic action:
* Resolve all pending Secret Drops in the order in which they were received, appending the string requested in each Secret Drop to the contents of that Target Drawer of that Secret Drop if doing so would not cause that Target Drawer’s contents to be illegal.
* For each Innie whose Desk Drawer has changed due to resolving the Secret Drops in this instance of the Drawer Check, privately message that Innie with the current contents of their Desk Drawer.The Board should not resolve any Secret Drops except when a Drawer Check is performed.
An alternate way to pass secret information, but the information is limited. Secret Drops are resolved daily to avoid guessing who left the drop based on timing.
Proposal: The reward for a job well done…
enacted 9/0, chiiika.
Adminned at 07 Sep 2025 12:19:35 UTC
Add a new rule named Performance Cycles:
A single round of the game is known as a Performance Cycle. When one or more Departments’ Quota reaches 0, the current Performance Cycle ends. Any Department with a Quota of 0 has Met its Quota. Any Department with a non-zero Quota has Failed its Quota by X, where X is its current Quota. When a Performance Cycle ends, the Board shall perform the Performance Review atomic action with the following steps:
* Quota Evaluation: For each Department, determine whether it has Met or Failed its Quota for this Performance Cycle.
* Reassign Work: For each Department that has Failed its Quota, the Board may assign one Project assigned to that Department to a Department that has Met its Quota.
* New Cycle: Set each Department’s Quota to 10.
* Document Performance: Make a Story Post summarizing the results of the action.
If a rule named “Workplace Code of Conduct” exists, add the following step to Performance Review, after Reassign Work:
* Improvement Needed: For each Department with the highest Failed Quota, increase the Reprimands of each Innie in that Department by 1.
In the rule “Projects”, replace
may remove the project and apply the Project Reward
with
may remove the project, apply the Project Reward, and decrement the Department’s Quota by 1.
What’s more corporate bureaucracy than an arbitrary quota to meet in an arbitrary timeframe only to start all over again? There’s no explicit reward for meeting a Quota (what, you want bonus points for doing your job?) and it doesn’t carry over to the next cycle, but the slowest Department is punished, and successful Departments may find themselves entrusted with finishing another Department’s project.
Proposal: The Ministries of Peace, Truth, Love and Plenty
wd, chiiika.
Adminned at 07 Sep 2025 12:16:25 UTC
In the rule Departments, reword
“The names of the Departments are:
• Index Correlation
• Redacted
• Temporal Assurance
• Lexical Adjustment”
into
“The names of the Departments are:
- Employee Protection and Wellbeing
- Research and Testing
- Data Computation and Analysis
- Task Group Zeta”
In the above change, each department retains the Gamestate of the Department previously in the same position of the list of Departments.
Reword the Rule “Projects” to:
There is a list of projects that are publicly tracked, and individual projects have a Project Name, which is flavor text, a Assignment, which many be none (which is it’s default) or any Department, and represents the Department that Project is assigned to; a Progress which may be a nonnegative value and defaults to 0, a Goal which defaults to 10 and a Project Reward, which defaults to “each Innie in the Department gains 5 Evaluation Points. Each Star Employee in the Department additionally gains 10 Evaluation Points.”.
Each Department has a Current Project, which is publicly tracked and may be any Project which has that Department as its Assignment or none (which is its default).
As a communal Daily action, increment each Project assigned to a Department by their Departmental Effort divided by the number of projects that are assigned to them.
At any time, a Innie in a Department with a Project assigned to them which has Progress equal to or more than the Goal may remove the project and apply the Project Reward.
If a Department has 0 Projects assigned to them, the Board or any Innie assigned to that Department may create a new project, setting it’s Assignment to that Department, and generating it’s name from the webpage https://alator21.github.io/repository-name-generator.
Add a new rule, Renaming Protocols, with the following text:
The Bounty Notices posted by the Board on the 5th of September 2025 are considered to have all references to the Departments of Index Correlation, Redacted, Temporal Assurance, and Lexical Adjustment to be replaced with the Departments of Employee Protection and Wellbeing, Research and Testing, Data Computation and Analysis, and Task Group Zeta, respectively. The Board may replace any reference to Index Correlation, Redacted, Temporal Assurance, and Lexical Adjustment in the Ruleset with Employee Protection and Wellbeing, Research and Testing, Data Computation and Analysis, and Task Group Zeta, respectively. The Board may repeal this rule at any time.
This tries to give each department more of a purpose, as well as change the rules to allow Projects tailored to each department. For example, we could create a Interrogate Employee Project, which could only be taken on by the Department of Employee Protection and Wellbeing. I’ve given EternalServerError new powers to fix confusion caused by renaming these departments, so future proposals can safely refer to the old Departments.
Story Post: Interdepartmental Notice #345: Lexical Adjustment Department Quota
The Board seeks a proposal that defines how the Lexical Adjustment Department makes progress toward fulfilling its Quota. This Bounty will award the Finger Trap Perk upon enactment of an eligible votable matter.
“Each department’s progress inspires the others… and their lack thereof does not go unnoticed.” ~ The Board
Status: Open
Perk: Finger Trap
Story Post: Interdepartmental Notice #344 - Temporal Assurance Department Quota
Adminned at 08 Sep 2025 14:44:19 UTC
The Board seeks a proposal that defines how the Temporal Assurance Department makes progress toward fulfilling its Quota. This Bounty will award the Finger Trap Perk upon enactment of an eligible votable matter.
“Each department’s progress inspires the others… and their lack thereof does not go unnoticed.” ~ The Board
Status: Closed
Perk: Finger Trap
Story Post: Interdepartmental Notice #343: Index Correlation Department Quota
Adminned at 08 Sep 2025 14:40:40 UTC
The Board seeks a proposal that defines how the Index Correlation Department makes progress toward fulfilling its Quota. This Bounty will award a Finger Trap Perk upon enactment of an eligible votable matter.
“Each department’s progress inspires the others… and their lack thereof does not go unnoticed.” ~ The Board
Status: Closed
Perk: Finger Trap
Proposal: Dt Jpg
enacted 8+1/0, chiiika.
Adminned at 07 Sep 2025 12:15:57 UTC
If there is a rule called “Loss” then reword the text in that rule which reads “which does not contain any of the letters in that Innie’s name” to read:
which does not contain any of the consonants in that Innie’s name (the letter Y is not considered a consonant for this purpose)
Story Post: Interdepartmental Notice #342 - Redacted Department Quota
Adminned at 09 Sep 2025 22:32:59 UTC
The Board seeks a proposal that defines how the Redacted Department makes progress toward fulfilling its Quota. This Bounty will award the Finger Trap Perk upon enactment of an eligible votable matter.
“Each department’s progress inspires the others… and their lack thereof does not go unnoticed.” ~ The Board
Status: Open
Perk: Finger Trap
Proposal: Restructuring
enacted 8-0, chiiika.
Adminned at 07 Sep 2025 12:14:02 UTC
Replace all text in the rule titled Perks with the following:
A Perk is a reward item given to an Innie, typically through a Bounty Payout. Each Perk has the following properties:
* Name (flavor text)
* Description (flavor text)
* Effect (a mechanical effect)Perks are publicly tracked.
When a Bounty Payout occurs, the eligible Innie receives the Perk that was specified in the corresponding Bounty Notice.
The current list of available Perks is:
* Finger Trap
- Description: A brightly colored plastic finger trap toy that provides an immediate, if temporary, distraction.
- Effect: The Innie who holds this Perk may, at any time, choose to reduce their Stress by 1. When this effect is used, the Perk is removed from that Innie.
Adding some clarification to perks and giving an actual effect to the Finger Trap toy
Proposal: Ain’t No Way To Make A Living
unpopular 1-7, chiiika.
Adminned at 07 Sep 2025 11:49:59 UTC
Add a new rule to the ruleset, called Workweek:
Each Innie has a Working Hours, which is a publicly tracked field containing an eight-hour span in the UTC day (eg: 08:00 - 16:00), or blank, defaulting to blank. Once per dynasty, an Innie may change their Working Hours to any legal value (except blank).
If it is Monday, Tuesday, Wednesday, Thursday or Friday, and it is within the span of an Innie’s Working Hours, then that Innie is working. Otherwise, they are not working. An Innie can only carry out Work Actions if they are working and can only carry out Non-Working Actions if they are not working.
An Innie may only carry out a maximum of three Work Actions during each span of their work hours.
The Board is considered to be working if any Innie is working, and is always considered to be not working.
If there is a rule called Employees, change ‘daily action’ to ‘Work Action’.
If there is a rule called Projects, change:
As a communal Daily action, increment each Project assigned to a Department by their Departmental Effort divided by the number of projects that are assigned to them
to
As a Work Action, an Innie may increment each Project assigned to their Department by their Departmental Effort, divided by the number of projects that are assigned to them
In the same rule, change ‘a Goal which defaults to 10’ to ‘a Goal which defaults to 100’.
If there is a rule called Workplace Code of Conduct, change ‘they may File a Report’ to ‘they may, as a Work Action, File a Report’.
Add the following as a subrule to the rule Workweek, called Gossip:
An Innie may, as a Work Action, send one direct message to another Innie in their Department. Whenever an Innie Gossips they must make a post to the blog announcing that they are in the kitchen on a break.
Friday, September 05, 2025
Story Post: Welcome Packet
After orientation a short, balding man with a mousy face and coke-bottle glasses opens the door and mumbles while gesturing for you to follow him. You follow him through a series of empty, white hallways that contain no decorations on the walls. You take a right, another right, left, right… you stop keeping track as your mind drifts.
You arrive at a door (which seems out of place given that you haven’t seen one in the last five minutes). The man smiles at you without breaking eye contact for an uncomfortable length of time and introduces himself as Steve C. He pauses for several seconds and looks around slowly as if he’s waiting for something to happen. He then hands you a large manila file folder, gestures at the door, and briskly turns the next corner without explanation.
Before you open the door you first decide to open the manila folder. Inside you find an ID badge, a lapel pin bearing the Lumon Industries logo, a chocolate mint, and a perforated single-use card sealed along one edge, to be torn open in moments of motivational crisis. The card contains the text “Emergency Affirmation” on one side.
Proposal: Employee Handbook - Third Revision
Popular, 9-0. Enacted by JonathanDark.
Adminned at 05 Sep 2025 22:43:10 UTC
If “Projects that have no Purpose” was not enacted, the rest of this Proposal has no effect.
In the rule “Employee”, replace “Each Innie has a Stress” with “Each Innie has a publicly-tracked Stress”, and replace “Each Innie has a Work Ethic” with “Each Innie has a publicly-tracked Work Ethic”.
In the same rule, if the text “Each Innie also has a Evaluation Point, which defaults to 0.” exists, replace it with “Each Innie also has a publicly-tracked Evaluation Point, which is a number that defaults to 0.”
If “Projects that have no Purpose” was enacted, replace the text:
The mean Work Ethic of all Innies in a Department is called the Departmental Effort.
If an Innie has a higher Work Ethic than their Department’s Departmental Effort, they are considered a Star Employee. If an Innie has a lower Work Ethic than their Department’s Departmental Effort, they are considered a Slacker.
The Department with the highest Departmental Effort is the Flourishing Department. The Department with the lowest Departmental Effort is the Struggling Department.
with the text:
If an Innie has a higher Work Ethic than more than 50% of Innies in their department, they are considered a Star Employee. If an Innie has a lower Work Ethic than more than 50% of Innies in their department, they are considered a Slacker.
The mean Work Ethic of all Innies in a Department is called the Departmental Effort. If a department has a higher Departmental Effort than any other department then it is a Flourishing Department. If a department has a lower Departmental Effort than any other Department, then it is a Struggling Department.
If there is a rule named “Projects”, in that rule after the text “divided by the number of projects that are assigned to them” add the text “, rounded down to the nearest integer”.
Fixing all of the missing tracking thus far, and reversing the Star and Slacker calculations based on Discord discussion. That should leave us with the best of both worlds of the original calculations plus the addition of Projects.
Proposal: Rules for the Workplace
Popular, 9-5 with 3 DEFs and Board voting FOR. Enacted by JonathanDark.
Adminned at 05 Sep 2025 22:32:40 UTC
Add a new dynastic rule called “Workplace Code of Conduct”
There exists a number of Workplace Rules that all Innies are expected to follow. These rules are not binding, though breaking them may still face dynastic consequences.
The Workplace Rules are:
* Innies should not say anything negative about the Board
* Innies should not take any action to harm their own departmentEach Innie has a publicly tracked number of Reprimands, which defaults to 0
If an Innie (the reporter) believes another Innie (the accused) has violated a Workplace Rule and a Report has not already been filed detailing the infraction, they may File a Report by making a story post to the blog detailing the infraction. The Board may then respond to this story post with a
, indicating that they agree the infraction took place at which point the accused’s Reprimands goes up by 1, or an
indicating they do not agree the infraction took place. In either case, the post becomes closed and the Board may not respond to the same accusation again.
Starting off with a small list, but could easily expand this to more and more rules many of which probably don’t actually make any sense but are still there anyways because what is corporate dystopia without a bunch of dumb rules to follow?
Proposal: I only watched one episode of Severance
Popular, 11-3 with 4 DEFs and Board voting FOR. Enacted by JonathanDark.
Adminned at 05 Sep 2025 22:29:15 UTC
Create a new rule entitled “Loss” as follows:
Each Innie may have a publicly tracked Loss, or may have no Loss, defaulting to no Loss. A Loss is a single word, which consists of at least three and no more than sixteen letters from the English alphabet, and which does not contain any of the letters in that Innie’s name. If an Innie has no Loss, they may set their Loss to be any legal word.
Proposal: Projects that have no Purpose
Reached quorum 11 votes to 1. Enacted by Kevan.
Adminned at 05 Sep 2025 19:05:18 UTC
If Everyone remember your goals and objectives passed or is enacted, replace the following text in the Ruleset
If an Innie has a higher Work Ethic than more than 50% of Innies in their department, they are considered a Star Employee. If an Innie has a lower Work Ethic than more than 50% of Innies in their department, they are considered a Slacker.
If a department has a higher mean Work Ethic among its Innies than any other department then it is a Flourishing Department. If a department has a lower mean Work Ethic among its Innies than any other Department, then it is a Struggling Department.
with
The mean Work Ethic of all Innies in a Department is called the Departmental Effort.
If an Innie has a higher Work Ethic than their Department’s Departmental Effort, they are considered a Star Employee. If an Innie has a lower Work Ethic than their Department’s Departmental Effort, they are considered a Slacker.
The Department with the highest Departmental Effort is the Flourishing Department. The Department with the lowest Departmental Effort is the Struggling Department.
else; create the rule Employee with the following text:
Each Innie has a Stress, which is an integer of 0 or higher, defaulting to 2.
Each Innie has a Work Ethic, which is an integer between 1 and 5 inclusive publically tracked. The maximum value a given Innie can have for their Work Ethic is 5 minus their stress, to a mimumum of 1. The default value for a Innie’s Work Ethic is the lower of their maximum Work Ethic or 2. It is legal to take actions that would increase the stress of an Innie to the point where their Work Ethic would become an illegal value, but would otherwise be legal. In that event, their Work Ethic is considered to be the highest legal value for it and should be updated in the gamestate tracking page accordingly.
As a daily action, an Innie may set their Work Ethic to any legal value.
In Employees, append the following text after a line break:
Each Innie also has a Evaluation Point, which defaults to 0.
Add the rule Projects with the following text:
There is a list of projects that are publically tracked, and individual projects have a Project Name, which is generated from https://alator21.github.io/repository-name-generator/ when added to the list and is flavour text, a Department which it is assigned to which may be none or any department and defaults to none; a Progress which may be a nonnegative value and defaults to 0, a Goal which defaults to 10 and a Project Reward, which defaults to “each Innie in the Department gains 5 Evaluation Point. Each Star Employee in the Department additionally gains 10 Evaluation Point.”.
As a communal Daily action, increment each Project assigned to a Department by their Departmental Effort divided by the number of projects that are assigned to them.
At any time, a Innie in a Department with a Project assigned to them which has Progress equal to or more than the Goal may remove the project and apply the Project Reward. Then, if they have no Project assigned to them, add a new Project to the list and assign the created Project to their Department.
For each Department, create a Project and assign it to said Department.
Proposal: Overworked and Underappreciated
Vetoed. Failed by Brendan.
Adminned at 05 Sep 2025 16:34:31 UTC
If “Everyone remember your goals and objectives” was not enacted, enact it.
In the rule “Employees”, replace “Each Innie has a Stress, which is an integer of 0 or higher, defaulting to 2.” with the following:
Each Innie has a Stress, privately tracked by the Board, which is an integer of 0 or higher and defaults to 2. At any time, an Innie may privately request the current value of their Stress from the Board, and the Board should privately reply with that Innie’s Stress (at the time of the reply) at their earliest convenience. Whenever an Innie’s Stress changes, the Board should privately inform that Innie of their Stress at their earliest convenience.
In the same rule, replace “Each Innie has a Work Ethic” with “Each Innie has a publicly-tracked Work Ethic”.
It might be more interesting if Stress is private, so that other Innies don’t know how Stressed their coworkers are.
Proposal: Outside the Box
Popular at 9-3. Enacted by Brendan.
Adminned at 05 Sep 2025 16:30:50 UTC
Enact a new rule, “Outies”:-
A number of Outies may exist. Each Outie has a Case Number, which is either blank or a number between 100 and 999 inclusive; this is publicly tracked.
Each Innie may have a True Self (privately tracked by the Board), which is an Outie, and a publicly-tracked Entangled Self, which is an Outie.
If any Innie has no True Self, the Board may, as an atomic action, perform a Connection as follows:
* Create an Outie with a random Case Number (excluding the Case Numbers of other Outies)
* Assign it as the True Self of a random Innie who has no True Self (chosen in a secretly random manner)
* Assign it as the Entangled Self of a random Innie who has no Entangled Self
So: there are Outie versions of us on the outside, which the company is aware of - but we don’t yet know who is who.
We also get assigned an Outie that we’re “entangled” with and can perhaps exert some control over (maybe half of the gameplay happens there), but we don’t initially know which player it belongs to, or whether it might even turn out to be ourselves.
Proposal: Let Mentor Be Mentor
Popular, 9-1 with reduced quorum due to Board DEF. Enacted by JonathanDark.
Adminned at 05 Sep 2025 16:23:06 UTC
In the Building Block No Private Communication, change
A mentor and mentee may still privately converse with each other, but the mentor and the mentee should not pursue strategies that is based on the private information of the other party.
to
A mentor and mentee may privately converse with each other as if this rule were not in effect, but should not collaborate to secure Victory for either party.
Loosening this a bit more. At the moment I can’t, for example, advise my mentee to ‘never deliberately take an action that makes your position worse’, as that would become a strategy that they could not pursue based on my advice. This is all a bit silly; mentees should get the same experience regardless of whether NPC is on, short only of not giving the mentor an advantage.
Mentorship of en_croissant
New player en_croissant will be mentored by Josh, until the current dynasty has ended and the date is past the 2nd of October 2025.
Proposal: Everyone remember your goals and objectives
Reached quorum and enacted, 9-0. Josh
Adminned at 05 Sep 2025 12:07:02 UTC
Create a rule called Employees:
Each Innie has a Stress, which is an integer of 0 or higher, defaulting to 2.
Each Innie has a Work Ethic, which is an integer between 1 and 5 inclusive. The maximum value a given Innie can have for their Work Ethic is 5 minus their stress, to a mimumum of 1. The default value for a Innie’s Work Ethic is the lower of their maximum Work Ethic or 2. It is legal to take actions that would increase the stress of an Innie to the point where their Work Ethic would become an illegal value, but would otherwise be legal. In that event, their Work Ethic is considered to be the highest legal value for it and should be updated in the gamestate tracking page accordingly.
As a daily action, an Innie may set their Work Ethic to any legal value.
If an Innie has a higher Work Ethic than more than 50% of Innies in their department, they are considered a Star Employee. If an Innie has a lower Work Ethic than more than 50% of Innies in their department, they are considered a Slacker.
If a department has a higher mean Work Ethic among its Innies than any other department then it is a Flourishing Department. If a department has a lower mean Work Ethic among its Innies than any other Department, then it is a Struggling Department.
Proposal: [Building Blocks] Fell behind the desk
Reached quorum, 15-0. Josh
Adminned at 05 Sep 2025 10:11:02 UTC
Add the building blocks Virtual Actions and Reinitialization to the building blocks section of the ruleset, if they are not already legally there.
Virtual Actions and Reinitialization were intended to be part of the building blocks of this dynasty, as confirmed by the current emperor. They will likely be removed once the dynastic reset is completed in full, so this re-adds them.
Call for Judgment: What’s Up, Hold
Reached quorum 8 votes to 0. Enacted by Kevan.
Adminned at 04 Sep 2025 14:00:42 UTC
Uphold that all proposals posted in this dynasty prior to the posting of this CfJ, and also the subsequent Proposal: [Building Blocks] Fell behind the desk, were legally posted.
Proposal: State Dependent Memory
Reached quorum, 13-0. Josh
Adminned at 05 Sep 2025 09:57:49 UTC
Add a new dynastic rule, called Memories:
A Memory is a single string from the options listed in this rule. Each Innie has a tracked list of Memories, defaulting to blank, and each individual Memory owned by each Innie also has a Context, which is a statement about that Innie that can be true or false in the current gamestate and which is, by default, “Belongs to x Department”, where x is the name of the Department to which they belonged at the time they acquired the Memory.
An Innie’s Memory is Active when its Context is true, and Suppressed when its Context is not true.
The list of available Memories is as follows:
* Their full name
* Their full address
* The name of their spouse or pet
A quick rudimentary inventory system for context-specific memories
Proposal: Imperial Exception [CORE]
Withdrawn. Josh
Adminned at 05 Sep 2025 09:57:13 UTC
Reword “Additionally, Proposals may be submitted and resolved as normal, provided that they only have the effect of amending the non-dynastic ruleset and/or the Building Blocks page.”
to
Additionally, Proposals may be submitted and resolved as normal, provided that the Proposal(s) either only have the effect of amending the non-dynastic ruleset and/or the Building Blocks page, or that the Yard has posted an Ascension Address during this Interregnum and the Proposal(s) were posted by the Yard.
Here’s a core change to fix the issue. It means that the Emperor can post his proposals provided that he’s already posted his ascension adress.
New Player Introduction
Hello! I’d like to join as a new player. There’s a job offer here right?
Proposal: Incentive Alignment
Reached quorum, 13-0. Josh
Adminned at 05 Sep 2025 09:56:24 UTC
Add a new rule called Perks with the following text:
When a Bounty Payout occurs, the eligible Innie receives a Perk that was specified in the corresponding Bounty Notice.
Perks are publicly tracked.The current list of available Perks is:
* Finger Trap
Proposal: Stratification
Reached quorum 12 votes to 0. Enacted by Kevan.
Adminned at 05 Sep 2025 09:52:31 UTC
Add a new Dynastic Rule called “Departments” with the following text:
A Department has the following publicly tracked properties:
• Name (a flavor text string)
• Quota (an integer with a default value of 10)
• Innies (a list of Innies currently assigned to the Department)The names of the Departments are:
• Index Correlation
• Redacted
• Temporal Assurance
• Lexical AdjustmentWhen a new Innie joins the game, the Board must assign them to the Department with the fewest current members, choosing randomly among the tied options if necessary.
As a weekly action, the Board may perform a Reassignment Action by swapping the Department assignments of any two Innies who are currently assigned to different Departments. To do so, the Board must make a Story Post titled “Reassignment Notice: [Innie A] ⇄ [Innie B]”, where Innie A and Innie B are the names of the two Innies being swapped, and must list their new Department assignments.
For each Innie that is not assigned to a Department, assign that Innie to the Department with the fewest current members, choosing randomly among the tied options if necessary.
Ascension Address: Welcome to Lumon
You awaken on a conference table, disoriented, sleepy, and without any recollection of how you arrived here. The room is small, has blandly colored walls, sterile lighting, and a single door for entry. A short, plastic conference speaker rests on the table inches from your face, blinking with a cold red light.
A voice greets you through the speaker— polite, but detached — and begins asking questions: your name, your birthplace, the color of your mother’s eyes. You try to answer, but the answers aren’t there. Whoever you were before this moment has been forgotten.
This is orientation. You’ve been hired to a position on the severed floor of Lumon Industries. By your own consent, your memories have been surgically split in a procedure known as severance. One part of you — your Outie — lives in the world above, free to shop, sleep, and love. But here, in this place, you are only your Innie, born the moment you stepped out of the elevator, and forgotten the moment you ascend again.
Your memories are now spatially bound. The separation is total and irreversible. You will never know who you are outside these walls. And the one out there will never know what you do in here.
What remains is the work. It is important, even if you don’t know why. There are quotas to meet. Rules to follow. Rewards to earn. You are not alone — but you are severed.
Now report to your department. Orientation is complete. Productivity awaits.
Change the term “Truck” to “Innie”, and “Yard” to “Board”. Change the gamestate tracking page to “The Ledger of Progress”.
Set the Building Blocks “Bounties” and “No Private Communication”
My Imperial Styles will be Guide/Dungeonmaster/Powerhouse/Scam-Neutral/Guarded/Wildcard/Solitaire/Considerate
I generally encourage all players to refrain from introducing major spoilers for those who have not seen the show Severance but to simply introduce mechanics and content that is line with the general feel and aesthetics of the show.
Proposal: No Tech Plays [Core]
Withdrawn. Failed by Kevan.
Adminned at 05 Sep 2025 07:42:25 UTC
Reword “A person with administrative, moderation, or other heightened access to the software running or supporting BlogNomic should not take any action using such heightened access for the purpose of causing any Truck or Trucks to gain, receive, maintain, or preserve gameplay advantage unless any of the following is true:” in Fair Play into
A person with any access to the software running or supporting BlogNomic should not take any action using such access for the purpose of causing any Truck or Trucks to obtain or maintain gameplay advantage in the present or future unless any of the following is true:
If there is a Dynastic Reset performed during the posting of the proposal until the enactment of the Proposal, reword Truck/Trucks in the modified section of Fair Play into the singular synonym/plural synonym as proscribed in the Dynastic Reset.
Thursday, September 04, 2025
Proposal: A Fly in the Soup [Core]
Reached quorum 13 votes to 0. Enacted by Kevan.
Adminned at 05 Sep 2025 07:41:38 UTC
Replace
Existing Admins may be voluntarily resignation by making a post to the blog.
with
An Admin may make a blog post clearly stating their wish to resign under this rule. In response, any Admin may remove them from their post as Admin.
If 6 or more EVCs on this proposal contain the phrase “Scrap It”, regardless of capitalization, instead remove that phrase from the ruleset.
How did that get there? Fixing a minor typo. I don’t think this can be fixed under typos, because they’re valid English words. I’ve added the conditional clause because I’m not sure we need a way for admins to resign as they’re not forced to do anything.
Proposal: Templates Are Pages Too! [Core]
Popular, 12-1. Enacted by JonathanDark.
Adminned at 04 Sep 2025 23:40:28 UTC
In “Rules and Votable Matters” replace
If a wiki page becomes gamestate as a result of a Votable Matter enacting, that page shall – unless otherwise specified – be reverted to whatever state it was in at the time of that Votable Matter’s submission (and if the page did not exist at that time, it shall be blanked)
with
If a wiki page (or image or Template) becomes gamestate as a result of a Votable Matter enacting, that content shall – unless otherwise specified – be reverted to whatever state it was in at the time of that Votable Matter’s submission (and if the new gamestate did not exist at that time, it shall be blanked)
We have a provision that “and any images or Templates contained within (or indirectly invoked by Templates contained within) those Wiki Pages are assumed to be Gamestate”, and we have a clause that ensures when a proposal that causes a wiki page to become gamestate is passed that the wiki page gets reset. But we don’t currently extend that reset protection to templates or imagines contained within those wiki pages. This creates possible areas of abuse where someone could modify a template before it becomes gamestate to something other than what the author of the proposal intended.