On the sitemember

Guild cores

Who leads each core, when it plays, how many titulars it has and what is still missing.

What it does: A list of the guild's cores, each with who leads it, the schedule, how many titulars it has against the size and the openings by role. Clicking opens the core's page: the description, the titulars and the reserves by role, with level and item level, and what is missing.
Who sees it: Whoever shares a Discord server with the guild, in any game. The Queue of those who asked to join only shows to the core's Raid Leader and officers and to whoever manages the guild.
Where to find it: In cores, on the guild bar.

How it should behave

The list brings the same cores the game receives: forming, active and paused. A core that is still calling has no members, and a closed one is over.
Raid Leader, officer and raider are titulars, and a reserve is a reserve. Each person counts by the character that goes to the game.
With no confirmed character, the person takes the spot, shows by Discord name as waiting for a character and fills no role.
The openings are the size's targets minus the titulars, by role. formed is all spots taken and all targets met: the same count as /core info.
Only a spec the game knows fills a role: a guess could call a core complete.
The page writes nothing: joining, accepting and refusing stay on Discord.
The description, up to 280 characters, is edited in /core edit.
A core of 10 says it does not count toward progression attendance.

“This guild has no cores yet”: the federation is off or does not exist. Whoever configures the server switches it on in /council config.
In a federation with guilds of two games, each guild's page reads its own characters, and Discord reads Forever's: the numbers can differ.
The Queue shows no note on the request: /core apply asks for none.