<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Safety Standards Resources on ISS</title><link>/resources/</link><description>Recent content in Safety Standards Resources on ISS</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 1999-2026 Institutional Safety Standards Foundation. All Rights Reserved.</copyright><lastBuildDate>Sun, 12 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="/resources/index.xml" rel="self" type="application/rss+xml"/><item><title>Baseline Safety Audit Framework</title><link>/resources/safety-audit-framework/</link><pubDate>Tue, 31 Mar 2026 17:00:00 -0700</pubDate><guid>/resources/safety-audit-framework/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;This document outlines the primary empirical criteria utilized by the Consortium to evaluate institutional compliance with modern safety protocols.&lt;/p&gt;
&lt;h2 id="data-collection-methodology"&gt;Data Collection Methodology&lt;/h2&gt;
&lt;p&gt;We rely on decentralized data pools to aggregate incident reports, response times, and preventative measures.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Metric A:&lt;/strong&gt; Incident frequency per capita.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Metric B:&lt;/strong&gt; Average systemic response latency.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Metric C:&lt;/strong&gt; Implementation rate of peer-reviewed safety standards.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More exhaustive data subsets will be attached to this framework as they clear the review process.&lt;/p&gt;</description></item><item><title>Curated Learning Environments: Continuous Viewing Using Remote Casting</title><link>/resources/curated-learning-environments/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>/resources/curated-learning-environments/</guid><description>&lt;div class="p-5 mb-5 text-bg-dark rounded-4 border shadow-sm"&gt;&lt;h2 class="display-6 fw-bold mb-3"&gt;Less Friction. More Learning.&lt;/h2&gt;&lt;div class="lead mb-4"&gt;
 The goal of this workflow is simple: get quality educational content onto the screen and keep it there. By using casting instead of traditional remote-based navigation, facilitators can eliminate the interruptions that break focus, reduce the cognitive overhead of managing multiple devices, and create longer, more productive viewing sessions for learners of all ages.
 &lt;/div&gt;&lt;/div&gt;

&lt;h2 id="introduction-streamlined-access-to-content"&gt;Introduction: Streamlined Access to Content&lt;/h2&gt;
&lt;p&gt;The primary objective of this workflow is to initiate a curated stream of long-form, educational content that flows well with minimal interruptions. By casting instead of using a traditional on-screen menu with a remote, parents, educators, and facilitators can achieve the following:&lt;/p&gt;</description></item><item><title>Managing Task Isolation with Brave Browser Profiles</title><link>/resources/brave-browser-profiles-task-isolation/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>/resources/brave-browser-profiles-task-isolation/</guid><description>&lt;div class="p-5 mb-5 text-bg-dark rounded-4 border shadow-sm"&gt;&lt;h2 class="display-6 fw-bold mb-3"&gt;Strict Compartmentalization Without Additional Software&lt;/h2&gt;&lt;div class="lead mb-4"&gt;
 Browser profiles enforce hard boundaries between cookies, extensions, and browsing history. Combined with Windows Virtual Desktops, they create isolated workspaces that eliminate context switching and digital clutter — using only tools already present in the operating system and browser.
 &lt;/div&gt;&lt;/div&gt;

&lt;h2 id="what-profile-isolation-provides"&gt;What Profile Isolation Provides&lt;/h2&gt;
&lt;p&gt;Browser profiles are not cosmetic. Each profile maintains a completely separate state: its own cookie jar, its own extension set, its own saved credentials, and its own browsing history. A session authenticated in one profile has no visibility into another. Extensions installed in one profile do not run in another.&lt;/p&gt;</description></item><item><title>Modern Windows Shell Architecture: PowerShell and WinGet</title><link>/resources/modern-windows-shell-architecture/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>/resources/modern-windows-shell-architecture/</guid><description>&lt;div class="p-5 mb-5 text-bg-dark rounded-4 border shadow-sm"&gt;&lt;h2 class="display-6 fw-bold mb-3"&gt;From Legacy CLI to Object-Oriented Automation&lt;/h2&gt;&lt;div class="lead mb-4"&gt;
 The Windows shell environment has shifted fundamentally. The current standard is defined by three decoupled components: PowerShell 7+ as the shell, Windows Terminal as the host, and WinGet as the native package manager. For users re-entering the Windows ecosystem, understanding these boundaries is the prerequisite for everything else.
 &lt;/div&gt;&lt;/div&gt;

&lt;h2 id="the-core-paradigm-objects-over-strings"&gt;The Core Paradigm: Objects Over Strings&lt;/h2&gt;
&lt;p&gt;The defining difference between PowerShell and Unix-like shells is the pipeline. Bash passes text streams that require &lt;code&gt;grep&lt;/code&gt;, &lt;code&gt;sed&lt;/code&gt;, or &lt;code&gt;awk&lt;/code&gt; for parsing. PowerShell passes &lt;code&gt;.NET&lt;/code&gt; objects. Every cmdlet receives structured objects and emits structured objects — no string parsing required.&lt;/p&gt;</description></item><item><title>Optimizing Our Workspaces: Reclaiming Vertical Screen Real Estate</title><link>/resources/optimizing-workspaces-vertical-screen-real-estate/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>/resources/optimizing-workspaces-vertical-screen-real-estate/</guid><description>&lt;div class="p-5 mb-5 text-bg-dark rounded-4 border shadow-sm"&gt;&lt;h2 class="display-6 fw-bold mb-3"&gt;Every Pixel Occupied by Static UI Is a Pixel Removed from Active Research Data&lt;/h2&gt;&lt;div class="lead mb-4"&gt;
 Modern monitors are optimized for video playback, not research. Reading academic literature, reviewing code, and analyzing longitudinal datasets are all vertical tasks. The default Windows 11 taskbar consumes 48 pixels of vertical height with no native mechanism for reduction. Reclaiming that space is a measurable productivity improvement — not a cosmetic preference.
 &lt;/div&gt;&lt;/div&gt;

&lt;h2 id="the-problem-with-default-taskbar-geometry"&gt;The Problem with Default Taskbar Geometry&lt;/h2&gt;
&lt;p&gt;The 16:9 aspect ratio is a video format. It is not a research format. The reality of daily knowledge work is entirely vertical: document scrolling, code review, terminal output, dataset inspection. Every pixel of static operating system chrome is a pixel subtracted from the active working surface.&lt;/p&gt;</description></item><item><title>Optimizing Screen Capture Pipelines for LLM Workflows</title><link>/resources/screen-capture-pipelines-llm-workflows/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>/resources/screen-capture-pipelines-llm-workflows/</guid><description>&lt;div class="p-5 mb-5 text-bg-dark rounded-4 border shadow-sm"&gt;&lt;h2 class="display-6 fw-bold mb-3"&gt;Route Capture Data by Intent, Not by Default&lt;/h2&gt;&lt;div class="lead mb-4"&gt;
 Assembling context for LLM workflows requires pulling from disparate visual sources rapidly and without interruption. The default Windows 11 Snipping Tool introduces a forced choice: accept focus-breaking notifications, or silence them and lose the save interface. A systems approach routes capture data directly to clipboard or disk based on immediate intent — no notifications, no friction, no compromise.
 &lt;/div&gt;&lt;/div&gt;

&lt;h2 id="the-architectural-shift"&gt;The Architectural Shift&lt;/h2&gt;
&lt;p&gt;The Windows 11 Snipping Tool is a single-pipeline utility. Every capture follows the same path regardless of whether the output is needed for thirty seconds or thirty days. For high-volume LLM workflows — where most captures are transient context that will never be referenced again — this creates unnecessary overhead on every interaction.&lt;/p&gt;</description></item><item><title>The Systems Architect's Guide to Microsoft Edge Split Screen</title><link>/resources/edge-split-screen-guide/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>/resources/edge-split-screen-guide/</guid><description>&lt;div class="p-5 mb-5 text-bg-dark rounded-4 border shadow-sm"&gt;&lt;h2 class="display-6 fw-bold mb-3"&gt;Edge Split Screen: Two-Stream Cognition&lt;/h2&gt;&lt;div class="lead mb-4"&gt;
 Edge Split Screen is a two-pane, deterministic, low-overhead research accelerator embedded inside a single browser window. Its power comes from directional link routing, pane swapping and rebinding, keyboard-driven focus control, and stable anchor + volatile exploration patterns.
 &lt;/div&gt;&lt;/div&gt;

&lt;h2 id="conceptual-model"&gt;Conceptual Model&lt;/h2&gt;
&lt;p&gt;Edge Split Screen is a two-pane document multiplexer embedded inside a single browser window.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Shared tab strip&lt;/strong&gt; — both panes bind to the same tab namespace&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Independent document contexts&lt;/strong&gt; — each pane renders its own DOM&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Directional link routing&lt;/strong&gt; — deterministic control over where new content loads&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Persistent divider state&lt;/strong&gt; — pane proportions remain stable during session&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Context rebinding&lt;/strong&gt; — switching tabs affects only the focused pane&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This makes Split Screen a lightweight, zero-overhead alternative to external tiling window managers.&lt;/p&gt;</description></item><item><title>External Partners &amp; Data Sources</title><link>/resources/external-directory/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/resources/external-directory/</guid><description>&lt;p&gt;The Consortium aggregates data and cross-references frameworks with a variety of federal and academic institutions. Click any category below to expand the directory.&lt;/p&gt;
&lt;details class="mt-5 mb-4"&gt;
 &lt;summary class="fs-5 fw-bold text-primary user-select-none" style="cursor: pointer;"&gt;
 Federal Safety Agencies
 &lt;/summary&gt;

 &lt;div class="pt-3 pb-3 border-start border-primary border-3 ps-4 mt-2 bg-light rounded-end"&gt;
 &lt;ul&gt;
&lt;li&gt;

&lt;a class="link link--text" href="..."&gt;Department of Institutional Safety&lt;/a&gt; - Core federal guidelines.&lt;/li&gt;
&lt;li&gt;

&lt;a class="link link--text" href="..."&gt;National Data Pool&lt;/a&gt; - Raw incident reporting statistics.&lt;/li&gt;
&lt;/ul&gt;

 &lt;/div&gt;
&lt;/details&gt;

&lt;details class="mb-4"&gt;
 &lt;summary class="fs-5 fw-bold text-primary user-select-none" style="cursor: pointer;"&gt;
 Academic Research Partners
 &lt;/summary&gt;

 &lt;div class="pt-3 pb-3 border-start border-primary border-3 ps-4 mt-2 bg-light rounded-end"&gt;
 &lt;ul&gt;
&lt;li&gt;

&lt;a class="link link--text" href="..."&gt;The Safety Institute at University&lt;/a&gt; - Peer-reviewed journals.&lt;/li&gt;
&lt;li&gt;

&lt;a class="link link--text" href="..."&gt;Applied Policy Lab&lt;/a&gt; - Template drafting and review.&lt;/li&gt;
&lt;/ul&gt;

 &lt;/div&gt;
&lt;/details&gt;

&lt;details class="mb-4"&gt;
 &lt;summary class="fs-5 fw-bold text-primary user-select-none" style="cursor: pointer;"&gt;
 State-Level Compliance Boards
 &lt;/summary&gt;

 &lt;div class="pt-3 pb-3 border-start border-primary border-3 ps-4 mt-2 bg-light rounded-end"&gt;
 &lt;ul&gt;
&lt;li&gt;

&lt;a class="link link--text" href="..."&gt;California Institutional Standards Board&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;

&lt;a class="link link--text" href="..."&gt;New York Public Safety Commission&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

 &lt;/div&gt;
&lt;/details&gt;</description></item></channel></rss>