Williams linc (17 Ergebnisse)

Zustand: New.

PAP. Zustand: New. New Book. Shipped from UK. Established seller since 2000.

PAP. Zustand: New. New Book. Shipped from UK. Established seller since 2000.

Zustand: New.

PAP. Zustand: New. New Book. Shipped from UK. Established seller since 2000.

PAP. Zustand: New. New Book. Shipped from UK. Established seller since 2000.

Zustand: New.

PAP. Zustand: New. New Book. Shipped from UK. Established seller since 2000.

PAP. Zustand: New. New Book. Shipped from UK. Established seller since 2000.

Taschenbuch. Zustand: Neu. Neuware - This is the Implementation Edition (Book Two, 'Architecture and Verification') for architects and engineers, distinct from the Foundations Edition. Here's a back cover description in your voice, sharpened against that volume's actual scope.THE THREE-BODY PROBLEM OF CLASSIFIED AI Implementation Edition - Architecture and VerificationAn Authorizing Official does not sign architecture. The AO signs evidence.The Foundations Edition defined the eight properties a classified AI system must satisfy to be authorized. It did not tell you how to make them true, or how to prove they stayed true after the assessor went home.This volume does.Architecture and Verification is the engineering half of the framework. It builds the operational trust layer one component at a time: the Delegation Token that binds every agent action to a human and an intent, the Unified Activity Record that leaves nothing unlogged, the Agentic RAG gateway that enforces classification at the point of retrieval, and the Governance Engine that gates tools by deterministic policy rather than model instruction. Then it builds the accountability layer the AO actually reads: the evidence stream, policy-as-code, the risk register, and the operating picture.Part Three goes past the baseline. Policy-gated autonomy. Automated ATO pre-submission scanning. Cross-system federated trust. The mosaic effect. Runtime detection and posture. The verification stack that turns 'trust but verify' from a slogan into a control.One rule runs through all of it: if the control ran, evidence exists; if evidence does not exist, the control never ran.A less capable agent with a well-designed harness outperforms a more capable agent without one. The harness is the product.Written for system architects, developers, security engineers, and DevSecOps teams who build what the AO will authorize, and for the AO who has to read what they built. Read the Foundations Edition to understand the problem. Read this one when you are ready to build.…

Taschenbuch. Zustand: Neu. Neuware - Regulated AI governance is not a compliance problem. It is a three-body problem. Data protection, regulatory compliance, and business velocity pull every AI deployment in a bank, a hospital, a utility, or an insurer in three directions at once. Optimize for one and the other two degrade. Most organizations treat that tension as a tradeoff to be split down the middle. It is not a tradeoff.>Lagrange Points carries the five-component governance harness out of the classified networks it was built for and into commercial industry. Seventy percent of the federal architecture transfers without modification. This book maps the other thirty, the consent, fairness, and multi-jurisdictional gaps the defense framing never had to face, one sector at a time.>- The 70/30 transfer rule: what moves verbatim from federal AI governance to regulated industry, and what does not- Five sector Lagrange points: financial services, healthcare, energy and critical infrastructure, insurance, and the manufacturing, supply chain, and telecommunications triad- One evidence stream rendered into SOC 2, HIPAA, PCI-DSS, NERC CIP, and EU AI Act packages at once- The maritime lineage of modern governance, from Lloyd's coffee house and the Plimsoll line to SOLAS after the Titanic- The three failure modes that recur in every regulated sector, and the harness controls that close them.…

Taschenbuch. Zustand: Neu. Neuware - ou will not authorize a classified AI system from a whiteboard. You will authorize it from artifacts. The Foundations Edition diagnosed the problem. The Implementation Edition built the architecture. This is the volume you take to the work. The Practitioner's Edition compresses the theory into three recap chapters and turns the rest into forty-five worksheets, checklists, scorecards, and configuration templates you can fill in by hand or wire into your tooling. System Assessment Questionnaire. Authorization Threshold Checklist. Delegation Token Design Worksheet. RAG Architecture Configuration Template. Policy-as-Code Template Library. Evidence Stream Implementation Checklist. ATO Pre-Submission Readiness Scorecard. Governance Gate Definition. Runtime Detection Configuration. Prompt Injection Mitigation Checklist. Pre-Flight Checklist. Incident Response Playbook. A1-A7 Adversary Response Matrix. Authorization Package Assembly Checklist. Open to any worksheet and you get the same three things: what the property requires, the evidence the assessor will demand, and a line to write your answer on. No re-derivation. No reread. Every tool maps back to a P1-P8 property and an evidence tier, so nothing you fill in is decorative. The appendices carry the sample configurations, the testing scripts, the Quick Reference, and a Quick Start Guide that gets a minimal viable harness running before the next standup. If the control ran, evidence exists. If evidence does not exist, the control never ran. Written for security engineers, DevSecOps teams, system operators, and implementation teams with a deadline and an authorization package to assemble. Keep this volume on the desk, not the shelf.…

Paperback. Zustand: new. Paperback. This is the Implementation Edition (Book Two, "Architecture and Verification") for architects and engineers, distinct from the Foundations Edition. Here's a back cover description in your voice, sharpened against that volume's actual scope.THE THREE-BODY PROBLEM OF CLASSIFIED AI Implementation Edition - Architecture and VerificationAn Authorizing Official does not sign architecture. The AO signs evidence.The Foundations Edition defined the eight properties a classified AI system must satisfy to be authorized. It did not tell you how to make them true, or how to prove they stayed true after the assessor went home.This volume does.Architecture and Verification is the engineering half of the framework. It builds the operational trust layer one component at a time: the Delegation Token that binds every agent action to a human and an intent, the Unified Activity Record that leaves nothing unlogged, the Agentic RAG gateway that enforces classification at the point of retrieval, and the Governance Engine that gates tools by deterministic policy rather than model instruction. Then it builds the accountability layer the AO actually reads: the evidence stream, policy-as-code, the risk register, and the operating picture.Part Three goes past the baseline. Policy-gated autonomy. Automated ATO pre-submission scanning. Cross-system federated trust. The mosaic effect. Runtime detection and posture. The verification stack that turns "trust but verify" from a slogan into a control.One rule runs through all of it: if the control ran, evidence exists; if evidence does not exist, the control never ran.A less capable agent with a well-designed harness outperforms a more capable agent without one. The harness is the product.Written for system architects, developers, security engineers, and DevSecOps teams who build what the AO will authorize, and for the AO who has to read what they built. Read the Foundations Edition to understand the problem. Read this one when you are ready to build. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Paperback. Zustand: new. Paperback. ou will not authorize a classified AI system from a whiteboard. You will authorize it from artifacts. The Foundations Edition diagnosed the problem. The Implementation Edition built the architecture. This is the volume you take to the work. The Practitioner's Edition compresses the theory into three recap chapters and turns the rest into forty-five worksheets, checklists, scorecards, and configuration templates you can fill in by hand or wire into your tooling. System Assessment Questionnaire. Authorization Threshold Checklist. Delegation Token Design Worksheet. RAG Architecture Configuration Template. Policy-as-Code Template Library. Evidence Stream Implementation Checklist. ATO Pre-Submission Readiness Scorecard. Governance Gate Definition. Runtime Detection Configuration. Prompt Injection Mitigation Checklist. Pre-Flight Checklist. Incident Response Playbook. A1-A7 Adversary Response Matrix. Authorization Package Assembly Checklist. Open to any worksheet and you get the same three things: what the property requires, the evidence the assessor will demand, and a line to write your answer on. No re-derivation. No reread. Every tool maps back to a P1-P8 property and an evidence tier, so nothing you fill in is decorative. The appendices carry the sample configurations, the testing scripts, the Quick Reference, and a Quick Start Guide that gets a minimal viable harness running before the next standup. If the control ran, evidence exists. If evidence does not exist, the control never ran. Written for security engineers, DevSecOps teams, system operators, and implementation teams with a deadline and an authorization package to assemble. Keep this volume on the desk, not the shelf. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Paperback. Zustand: new. Paperback. This is the Implementation Edition (Book Two, "Architecture and Verification") for architects and engineers, distinct from the Foundations Edition. Here's a back cover description in your voice, sharpened against that volume's actual scope.THE THREE-BODY PROBLEM OF CLASSIFIED AI Implementation Edition - Architecture and VerificationAn Authorizing Official does not sign architecture. The AO signs evidence.The Foundations Edition defined the eight properties a classified AI system must satisfy to be authorized. It did not tell you how to make them true, or how to prove they stayed true after the assessor went home.This volume does.Architecture and Verification is the engineering half of the framework. It builds the operational trust layer one component at a time: the Delegation Token that binds every agent action to a human and an intent, the Unified Activity Record that leaves nothing unlogged, the Agentic RAG gateway that enforces classification at the point of retrieval, and the Governance Engine that gates tools by deterministic policy rather than model instruction. Then it builds the accountability layer the AO actually reads: the evidence stream, policy-as-code, the risk register, and the operating picture.Part Three goes past the baseline. Policy-gated autonomy. Automated ATO pre-submission scanning. Cross-system federated trust. The mosaic effect. Runtime detection and posture. The verification stack that turns "trust but verify" from a slogan into a control.One rule runs through all of it: if the control ran, evidence exists; if evidence does not exist, the control never ran.A less capable agent with a well-designed harness outperforms a more capable agent without one. The harness is the product.Written for system architects, developers, security engineers, and DevSecOps teams who build what the AO will authorize, and for the AO who has to read what they built. Read the Foundations Edition to understand the problem. Read this one when you are ready to build. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.…

Paperback. Zustand: new. Paperback. Regulated AI governance is not a compliance problem. It is a three-body problem. Data protection, regulatory compliance, and business velocity pull every AI deployment in a bank, a hospital, a utility, or an insurer in three directions at once. Optimize for one and the other two degrade. Most organizations treat that tension as a tradeoff to be split down the middle. It is not a tradeoff.In orbital mechanics, the point where competing forces hold an object in place has a name: a Lagrange point. Every regulated sector has one, and reaching it is an engineering problem, not a policy compromise. Lagrange Points carries the five-component governance harness out of the classified networks it was built for and into commercial industry. Seventy percent of the federal architecture transfers without modification. This book maps the other thirty, the consent, fairness, and multi-jurisdictional gaps the defense framing never had to face, one sector at a time.Inside this book: - The 70/30 transfer rule: what moves verbatim from federal AI governance to regulated industry, and what does not- Five sector Lagrange points: financial services, healthcare, energy and critical infrastructure, insurance, and the manufacturing, supply chain, and telecommunications triad- One evidence stream rendered into SOC 2, HIPAA, PCI-DSS, NERC CIP, and EU AI Act packages at once- The maritime lineage of modern governance, from Lloyd's coffee house and the Plimsoll line to SOLAS after the Titanic- The three failure modes that recur in every regulated sector, and the harness controls that close them This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.…

Paperback. Zustand: new. Paperback. ou will not authorize a classified AI system from a whiteboard. You will authorize it from artifacts. The Foundations Edition diagnosed the problem. The Implementation Edition built the architecture. This is the volume you take to the work. The Practitioner's Edition compresses the theory into three recap chapters and turns the rest into forty-five worksheets, checklists, scorecards, and configuration templates you can fill in by hand or wire into your tooling. System Assessment Questionnaire. Authorization Threshold Checklist. Delegation Token Design Worksheet. RAG Architecture Configuration Template. Policy-as-Code Template Library. Evidence Stream Implementation Checklist. ATO Pre-Submission Readiness Scorecard. Governance Gate Definition. Runtime Detection Configuration. Prompt Injection Mitigation Checklist. Pre-Flight Checklist. Incident Response Playbook. A1-A7 Adversary Response Matrix. Authorization Package Assembly Checklist. Open to any worksheet and you get the same three things: what the property requires, the evidence the assessor will demand, and a line to write your answer on. No re-derivation. No reread. Every tool maps back to a P1-P8 property and an evidence tier, so nothing you fill in is decorative. The appendices carry the sample configurations, the testing scripts, the Quick Reference, and a Quick Start Guide that gets a minimal viable harness running before the next standup. If the control ran, evidence exists. If evidence does not exist, the control never ran. Written for security engineers, DevSecOps teams, system operators, and implementation teams with a deadline and an authorization package to assemble. Keep this volume on the desk, not the shelf. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.…