{"version":"2.1.232","anchor":"storage-layout-reserves-a-place-for-per-day-session-logs","canonical_anchor":"storage-layout-reserves-a-place-for-per-day-session-logs","heading":"Storage layout reserves a place for per-day session logs","tier":"soon","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/storage-layout-reserves-a-place-for-per-day-session-logs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Storage layout reserves a place for per-day session logs\n\nStorage keys now reserve space for per-day session logs that nothing reads or writes.\n\n**What**\n\nThe storage key scheme adds a session-log area addressed by project, year, month, day and a log name, with validation on both the key and its scope. Nothing in this build reads or writes it; it exists only in the key builder and the validators.\n\n**Details**\n\n- Validation requires a four-digit year and two-digit month and day, a month only alongside a year, and a day only alongside a month.\n- The log name must be a short session id of up to eight word characters, optionally followed by a hyphenated lower-case title slug, and cannot be a bare device name.\n\n**Evidence**\n\n`must be the session-log stem <sessionId8>[-<title-slug>]: up to eight word characters, then lower-case a-z \/ 0-9 runs joined by single hyphens; not a bare device name`, `namespace: \"sessionLog\"`, `must be the session-log stem <sessionId8>[-<title-slug>]`\n\n- Area: Internals\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}