Update notice-records with definition of notice

bylaws/notice-records.md

@@ -8,7 +8,25 @@ This document describes the notice and record-keeping policies for the Commonhau
 
 ## Notice
 
-TBD
+The CF recognizes the importance of efficient and accessible communication, given that members will be globally distributed and predominantly remote. To ensure transparency and fair decision-making, the following guidelines clarify when notice is required and how members can expedite processes:
+
+### Notification Requirements
+
+- **GitHub Discussions:** Notification via GitHub Discussions is required for significant matters, including changes to the bylaws, project membership status, or any other decision requiring member input or approval.
+
+- **Email:** Sending an email to the designated email addresses described in these bylaws constitutes giving notice for most operational matters. Email notification is required for decisions that necessitate prompt action or are time-sensitive. 
+
+### Expedited Process
+
+Electronic notice is considered timely and effective when sent through these means. While oral communication remains an option, it is primarily intended for exceptional circumstances, given the remote nature of Foundation operations.
+
+For most decisions, a standard waiting period of at least 72 hours will be observed to allow time for objections and discussions (see [Decision Making][]).
+
+For substantive revisions to the bylaws, a standard review period of 30 days will be observed (see [Amendments][]).
+
+To expedite processes and reduce the time between posting the notice and taking action, members can collectively agree that formal notification is unnecessary. This decision can be made informally through email or GitHub Discussions and should consider the urgency of the matter. The emphasis is on timely action, and unnecessary delays should be avoided.
+
+CF and CFC members are encouraged to use this mechanism responsibly, ensuring that important decisions still receive the appropriate attention and discussion.
 
 ## Record Keeping
 
@@ -29,3 +47,6 @@ The CF will maintain records of all activities for transparency and legal compli
 - **Annual Reports** will be prepared and filed as per state and federal regulations, with accessibility as required by law.
 - **Retention and Version Control**: Documents will adhere to legal requirements for retention periods and employ version control for historical accuracy.
 - **Backup and Security:** Regular backups and robust security measures to safeguard digital records.
+
+[Amendments]: amendments.md
+[Decision Making]: decision-making.md#seeking-consensus-on-mailing-lists