From df3f65555e46e1b7d6149f71f084a39ab0e2b2ff Mon Sep 17 00:00:00 2001
From: Ian Grigg <iang@cacert.org>
Date: Sun, 24 Mar 2013 22:29:55 +0000
Subject: [PATCH] added clarificartion as to AO's role

git-svn-id: http://svn.cacert.org/CAcert/Policies@2490 14b1bab8-4ef6-0310-b690-991c95c89dfd
---
 NucleusAssurancePolicy.html | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/NucleusAssurancePolicy.html b/NucleusAssurancePolicy.html
index 7ea5454..ab8d483 100644
--- a/NucleusAssurancePolicy.html
+++ b/NucleusAssurancePolicy.html
@@ -79,7 +79,7 @@
   <h2 id="s2"> 2. The Nucleus Event </h2>
   <p id="s2.1"><b> 2.1 </b>
    A Nucleus event is a training and assurance event that brings many candidate
-   Assurers up to the level of Assurer in one day, by allocating
+   Assurers up to the level of Assurer in one event, by allocating
    the Assurance Points that they would be able to allocate, in advance.
   </p>
 
@@ -101,6 +101,13 @@
     <li>Proposed training programme.</li>
   </ul>
 
+  <p class="q">Note that this above clause does not give the AO the power to
+      stop or modify the activity.  Such responsibility is left
+      entirely with the Senior Asssurer.
+      The policy should seek to be self-maintaining and efficiently
+      distributable, so putting the AO in as a blocking step would
+      not be appropriate to that goal. </p>
+
   <p id="s2.4"><b> 2.4 </b>
    On the day, a quorum of Assurers and candidates must be found
    (as present and working).