feat(web): surface IwoooS progress acceleration lanes
This commit is contained in:
@@ -2708,6 +2708,51 @@
|
||||
"guard": "not_authorization=true; approval record=false"
|
||||
}
|
||||
}
|
||||
},
|
||||
"progressAcceleration": {
|
||||
"title": "Progress Acceleration And Real Unlock Points",
|
||||
"subtitle": "Progress is moving, but the 58% headline only gets reassessed when owner responses, runtime gates, GitHub primary readiness, or AwoooP production landing produce real evidence. This board makes the next visible unlock points explicit.",
|
||||
"laneLabel": "Acceleration lane",
|
||||
"unlockLabel": "Unlock signal",
|
||||
"guardLabel": "Low-friction boundary remains",
|
||||
"items": {
|
||||
"ownerResponses": {
|
||||
"title": "Converge owner responses first",
|
||||
"body": "S4.9-S4.12 owner responses for Gitea, GitHub targets, refs truth, and workflow / secret names are the main reason the headline is holding at 58%.",
|
||||
"unlock": "The headline can be reassessed only after the first accepted redacted owner responses arrive.",
|
||||
"guard": "Redacted evidence only; no repo creation, refs sync, workflow mutation, or secret value collection."
|
||||
},
|
||||
"redactedIngestion": {
|
||||
"title": "Connect redacted evidence ingestion",
|
||||
"body": "Security findings, Kali observe signals, and owner evidence need to enter the read-only intake plane as redacted metadata before runtime work.",
|
||||
"unlock": "Runtime landing gets a real signal only after the redacted payload ingestion adapter is approved and passes preflight.",
|
||||
"guard": "No raw payload, no credential plaintext, and no active scan."
|
||||
},
|
||||
"runtimeGate": {
|
||||
"title": "Runtime gates stay separately approved",
|
||||
"body": "Future scanning, repair, host update, or blocking controls must not auto-advance from frontend status.",
|
||||
"unlock": "Runtime landing can be reassessed only after S3 / S3.4 has human approval, rollback, post-check metrics, and an active runtime gate.",
|
||||
"guard": "active runtime gate=0; action button=false; Kali /execute remains a block candidate."
|
||||
},
|
||||
"githubReadiness": {
|
||||
"title": "Split GitHub primary readiness blockers",
|
||||
"body": "The long-term GitHub direction is agreed, but targets, refs, workflow / secret names, and rollback ADR still need full verification.",
|
||||
"unlock": "primary_ready_count can move only after owner responses, refs truth, workflow parity, and rollback ADR are verifiable.",
|
||||
"guard": "No primary switch, no force push, no refs deletion, and no unapproved target repo creation."
|
||||
},
|
||||
"awooopLanding": {
|
||||
"title": "Make AwoooP / IwoooS visible in the main flow",
|
||||
"body": "One reason progress feels slow is that security work still looks like backend contracts; the next steps, blockers, prohibitions, and unlock signals need to be visible in-product.",
|
||||
"unlock": "Once AwoooP consumes the rollup and IwoooS board read-only, users can see the real blockers directly.",
|
||||
"guard": "Read-only landing only; visible status is not authorization and does not add execution buttons."
|
||||
},
|
||||
"cadenceCompression": {
|
||||
"title": "Move future cadence in batches",
|
||||
"body": "S2.38-S2.45 split many checklist layers, making progress feel fragmented. Next work should favor P0 owner responses and AwoooP landing over endlessly adding small checklist layers.",
|
||||
"unlock": "Similar framework details should be batched in future reports; only high-level gate changes move the headline.",
|
||||
"guard": "Faster cadence does not loosen safety; runtime and source-control cutover still need human gates."
|
||||
}
|
||||
}
|
||||
}
|
||||
},
|
||||
"tickets": {
|
||||
|
||||
@@ -2709,6 +2709,51 @@
|
||||
"guard": "not_authorization=true;approval record=false"
|
||||
}
|
||||
}
|
||||
},
|
||||
"progressAcceleration": {
|
||||
"title": "進度加速與真正解鎖點",
|
||||
"subtitle": "目前不是沒有推進,而是 58% headline 只在 owner response、runtime gate、GitHub primary readiness 或 AwoooP production landing 有實質 evidence 時才會重估。這裡把下一批有感推進點集中顯示。",
|
||||
"laneLabel": "加速路線",
|
||||
"unlockLabel": "解鎖訊號",
|
||||
"guardLabel": "仍維持低摩擦邊界",
|
||||
"items": {
|
||||
"ownerResponses": {
|
||||
"title": "Owner responses 先收斂",
|
||||
"body": "S4.9-S4.12 的 Gitea、GitHub target、refs truth、workflow / secret name owner response 是目前 58% 最主要的卡點。",
|
||||
"unlock": "收到並驗收第一批脫敏 owner response 後,headline 才有重估依據。",
|
||||
"guard": "只收脫敏 evidence;不建立 repo、不同步 refs、不修改 workflow、不收 secret value。"
|
||||
},
|
||||
"redactedIngestion": {
|
||||
"title": "Redacted ingestion 接上可見證據",
|
||||
"body": "資安 finding、Kali observe 訊號與 owner evidence 需要先以 redacted metadata 進入只讀收件面,再談 runtime。",
|
||||
"unlock": "redacted payload ingestion adapter 經人工批准並通過 preflight 後,runtime landing 會有實質訊號。",
|
||||
"guard": "不收 raw payload、不收 credential plaintext、不啟動 active scan。"
|
||||
},
|
||||
"runtimeGate": {
|
||||
"title": "Runtime gate 必須獨立批准",
|
||||
"body": "後續真正掃描、修復、主機更新或 blocking control 都不能從前端狀態自動推進。",
|
||||
"unlock": "S3 / S3.4 有人工批准、rollback、post-check metrics 與 active runtime gate 後,才進入落地重估。",
|
||||
"guard": "active runtime gate=0;action button=false;Kali /execute 仍是 block candidate。"
|
||||
},
|
||||
"githubReadiness": {
|
||||
"title": "GitHub primary readiness 要拆關鍵缺口",
|
||||
"body": "Gitea 轉 GitHub 的大方向已確認,但 target、refs、workflow / secret name、rollback ADR 還沒全量驗證。",
|
||||
"unlock": "owner response、refs truth、workflow parity 與 rollback ADR 都可驗證後,primary_ready_count 才能往上。",
|
||||
"guard": "不切 primary、不 force push、不刪 refs、不建立未批准 target repo。"
|
||||
},
|
||||
"awooopLanding": {
|
||||
"title": "AwoooP / IwoooS 主線可見",
|
||||
"body": "使用者感覺慢的原因之一,是資安工作還太像後台契約;需要把下一步、卡點、禁令與解鎖訊號放到產品入口。",
|
||||
"unlock": "AwoooP 主線只讀消費 rollup 與 IwoooS 面板後,使用者能直接看到真正卡點。",
|
||||
"guard": "只讀 landing;不把可見狀態當授權,不新增執行按鈕。"
|
||||
},
|
||||
"cadenceCompression": {
|
||||
"title": "後續節奏改成批次推進",
|
||||
"body": "S2.38-S2.45 太多細層 checklist 讓進度看起來碎。後續應優先收斂 P0 owner response 與 AwoooP landing,而不是無限拆小核對項。",
|
||||
"unlock": "相同類型的 framework detail 之後合併成一批回報,只有高層 gate 變動才調整 headline。",
|
||||
"guard": "節奏加快不等於放寬安全;runtime 與 source-control cutover 仍需人工 gate。"
|
||||
}
|
||||
}
|
||||
}
|
||||
},
|
||||
"tickets": {
|
||||
|
||||
@@ -31,6 +31,13 @@ type PostureMetric = {
|
||||
tone: 'steady' | 'warn' | 'locked'
|
||||
}
|
||||
|
||||
type ProgressAccelerationLane = {
|
||||
key: string
|
||||
lane: string
|
||||
icon: typeof ShieldCheck
|
||||
tone: 'steady' | 'warn' | 'locked'
|
||||
}
|
||||
|
||||
type Pillar = {
|
||||
key: string
|
||||
icon: typeof ShieldCheck
|
||||
@@ -307,6 +314,15 @@ const postureMetrics: PostureMetric[] = [
|
||||
{ key: 'activeGates', value: '0', tone: 'locked' },
|
||||
]
|
||||
|
||||
const progressAccelerationLanes: ProgressAccelerationLane[] = [
|
||||
{ key: 'ownerResponses', lane: 'PAL1', icon: ClipboardCheck, tone: 'warn' },
|
||||
{ key: 'redactedIngestion', lane: 'PAL2', icon: FileText, tone: 'warn' },
|
||||
{ key: 'runtimeGate', lane: 'PAL3', icon: Lock, tone: 'locked' },
|
||||
{ key: 'githubReadiness', lane: 'PAL4', icon: GitBranch, tone: 'warn' },
|
||||
{ key: 'awooopLanding', lane: 'PAL5', icon: Radar, tone: 'steady' },
|
||||
{ key: 'cadenceCompression', lane: 'PAL6', icon: CheckCircle2, tone: 'steady' },
|
||||
]
|
||||
|
||||
const posturePillars: Pillar[] = [
|
||||
{ key: 'exposure', icon: Radar, tone: 'warn' },
|
||||
{ key: 'sourceControl', icon: GitBranch, tone: 'warn' },
|
||||
@@ -784,6 +800,38 @@ function MetricCard({ item }: { item: PostureMetric }) {
|
||||
)
|
||||
}
|
||||
|
||||
function ProgressAccelerationLaneCard({ item }: { item: ProgressAccelerationLane }) {
|
||||
const t = useTranslations('iwooos.progressAcceleration')
|
||||
const Icon = item.icon
|
||||
return (
|
||||
<div style={{ ...band, minHeight: 202, padding: 16 }}>
|
||||
<div style={{ display: 'flex', alignItems: 'center', justifyContent: 'space-between', gap: 12 }}>
|
||||
<div style={{ display: 'flex', alignItems: 'center', gap: 9 }}>
|
||||
<Icon size={18} color={toneColors[item.tone]} />
|
||||
<span style={{ fontSize: 11, color: '#87867f' }}>{t('laneLabel')}</span>
|
||||
</div>
|
||||
<span style={{ fontSize: 11, color: '#9b978b' }}>{item.lane}</span>
|
||||
</div>
|
||||
<h2 style={{ fontSize: 14, margin: '12px 0 6px', color: '#141413' }}>
|
||||
{t(`items.${item.key}.title` as never)}
|
||||
</h2>
|
||||
<p style={{ fontSize: 12, lineHeight: 1.55, color: '#6f6d66', margin: 0 }}>
|
||||
{t(`items.${item.key}.body` as never)}
|
||||
</p>
|
||||
<div style={{ marginTop: 10, display: 'grid', gap: 5 }}>
|
||||
<div style={{ fontSize: 11, color: '#87867f' }}>{t('unlockLabel')}</div>
|
||||
<div style={{ fontSize: 11, color: toneColors[item.tone], lineHeight: 1.45 }}>
|
||||
{t(`items.${item.key}.unlock` as never)}
|
||||
</div>
|
||||
<div style={{ fontSize: 11, color: '#87867f', marginTop: 4 }}>{t('guardLabel')}</div>
|
||||
<div style={{ fontSize: 11, color: '#6f6d66', lineHeight: 1.45 }}>
|
||||
{t(`items.${item.key}.guard` as never)}
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
)
|
||||
}
|
||||
|
||||
function PillarCard({ item }: { item: Pillar }) {
|
||||
const t = useTranslations('iwooos.pillars')
|
||||
const Icon = item.icon
|
||||
@@ -1968,6 +2016,26 @@ export default function IwoooSPage({ params }: { params: { locale: string } }) {
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<section style={{ marginBottom: 14 }}>
|
||||
<div style={{ marginBottom: 14 }}>
|
||||
<h2 style={{ fontSize: 16, margin: 0 }}>{t('progressAcceleration.title')}</h2>
|
||||
<p style={{ fontSize: 12, color: '#6f6d66', margin: '6px 0 0', lineHeight: 1.55 }}>
|
||||
{t('progressAcceleration.subtitle')}
|
||||
</p>
|
||||
</div>
|
||||
<div
|
||||
style={{
|
||||
display: 'grid',
|
||||
gridTemplateColumns: 'repeat(auto-fit, minmax(220px, 1fr))',
|
||||
gap: 12,
|
||||
}}
|
||||
>
|
||||
{progressAccelerationLanes.map(item => (
|
||||
<ProgressAccelerationLaneCard key={item.key} item={item} />
|
||||
))}
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<section style={{ marginBottom: 14 }}>
|
||||
<div style={{ marginBottom: 14 }}>
|
||||
<h2 style={{ fontSize: 16, margin: 0 }}>{t('journey.title')}</h2>
|
||||
|
||||
Reference in New Issue
Block a user