Cities Index.
Agenda packet

San Carlos City Council
October 23, 2023

Document
Agenda packet
Meeting
October 23, 2023
Body
San Carlos City Council
Original file
109.4 MB
Text extracted from the city's file for reading and search. Open the original on cityofsancarlos.primegov.com. That file is the official record.

CITY OF SAN CARLOS
City Council/Successor Agency to the
Redevelopment Agency/Housing Authority
Regular Meeting
October 23, 2023  7:00 PM
Council Chambers, City Hall
600 Elm Street, San Carlos, CA 94070
www.cityofsancarlos.org
AGENDA
This meeting will be conducted both in­person at City Hall and virtually via Zoom. Members of the public will have the option to observe the meeting and address the City Council as outlined below.

In­Person Participation:

Location. City Hall – 600 Elm Street, Council Chambers.

Masks are no longer required, but are still recommended by the California Department of Health. To maintain public health and safety, please do not attend in person if you are experiencing respiratory symptoms (e.g. cough, runny nose, and/or sore throat).

Provide Public Comment. To address the City Council on any item on the posted agenda, fill out a Request to Speak Form located in the back of the Council Chambers and submit it to the City Clerk; or, you may raise your hand when the Mayor calls for public comments.

Remote Participation:

Observe via:
­    Zoom. https://us02web.zoom.us/j/88256140939; or call 1­669­900­9128 and enter the Meeting ID #: 882 5614 0939
­    Meeting Webportal.  www.cityofsancarlos.org/agenda ­    Local TV. Comcast Channel 27 and AT&T Uverse Channel 99 Provide Public Comment. If you plan to make a public comment on any item on the posted agenda, please observe the meeting via Zoom (see above access information), and during the public comment period for the agenda item you wish to address, use the “raise hand” feature. If joining Zoom by phone, press *9 to “raise hand”.

Councilmembers may participate in this meeting remotely as authorized by Assembly Bill 2449.

MAYOR:  Adam Rak
COUNCIL:Ronald Collins, John Dugan, Sara McDowell, Pranita Venkatesh

1. CALL TO ORDER
1 ageda,peaseobseeteeetgaoo(seeaboeaccessoato),addugtepubc comment period for the agenda item you wish to address, use the “raise hand” feature. If joining Zoom by phone, press *9 to “raise hand”.

Councilmembers may participate in this meeting remotely as authorized by Assembly Bill 2449.

MAYOR:  Adam Rak
COUNCIL:Ronald Collins, John Dugan, Sara McDowell, Pranita Venkatesh

1. CALL TO ORDER

2. ASSEMBLY BILL 2449 TELECONFERENCE REQUESTS

3. PLEDGE OF ALLEGIANCE
Led by Boy Scout Troop 321.

4. CHANGES TO THE ORDER OF THE AGENDA

5. PRESENTATIONS
a. Present a City Coin to Community Volunteer Samina Ginwalla. b. Present a Proclamation Recognizing the 30  Anniversary of Art Bias. c. Present Proclamations to Jack Alger and Christos Daskarolis with Boy Scout Troop 321 Upon Receiving Their Eagle Scout Award.
d. Receive an Annual Report from the San Carlos Library.

6. COUNCIL COMMUNICATIONS AND ANNOUNCEMENTS
Council Communications and Announcements are brief items from members of the City Council regarding upcoming events in the community and correspondence that they have received. They are informational in nature and no action will be taken on these items at this meeting.

7. CONSENT CALENDAR
a. Motion to Waive Reading of All Ordinances.
b. Approve the September 11, 2023 City Council Regular Meeting Minutes. c. Adopt a Resolution Awarding the 2024 Sewer System Root Foaming Project C1752; Authorizing the City Manager to Execute a Public Projects Agreement with Duke’s Root Control, Inc. of Elgin, Illinois in the Amount of $150,678.45; and Authorizing the Expenditure of Contingency up to the Project Budget. d. Adopt a Resolution Adopting a Meeting Decorum and Civility Policy for Public Meetings.
e. Adopt Ordinance 1601 Approving the 841 Old County Road Project Planned Development Plan and Related Zoning Map Amendment to Rezone the Project Site from Heavy Industrial (IH) to Planned Development (PD) at 841 Old County Road (APNs 046­133­160, 046­134­050, 046­134­060, 046­135­010, 046­135­020, 046­ 135­030, 046­135­040, 046­182­100, 046­182­110, 046­182­150). f. Adopt Ordinance 1602 Approving a Development Agreement with the Sobrato FilFdtifth841OldCtRdPjt
th
2 C1752; Authorizing the City Manager to Execute a Public Projects Agreement with Duke’s Root Control, Inc. of Elgin, Illinois in the Amount of $150,678.45; and Authorizing the Expenditure of Contingency up to the Project Budget. d. Adopt a Resolution Adopting a Meeting Decorum and Civility Policy for Public Meetings.
e. Adopt Ordinance 1601 Approving the 841 Old County Road Project Planned Development Plan and Related Zoning Map Amendment to Rezone the Project Site from Heavy Industrial (IH) to Planned Development (PD) at 841 Old County Road (APNs 046­133­160, 046­134­050, 046­134­060, 046­135­010, 046­135­020, 046­ 135­030, 046­135­040, 046­182­100, 046­182­110, 046­182­150). f. Adopt Ordinance 1602 Approving a Development Agreement with the Sobrato Family Foundation, for the 841 Old County Road Project.

8. PUBLIC HEARING
a. Consideration of Introducing an Ordinance Amending San Carlos Municipal Code Title 18 ­ Zoning to Create Objective Design Standards for Single­Family Development.
b. Consideration of Introducing an Ordinance Amending the San Carlos Municipal Code Section 18.23.210 ­ Accessory Dwelling Units/Junior Accessory Dwelling Units and Sections 18.03 ­ Rules of Measurement, 18.12 ­ Hillside Overlay District,

18.29 ­ Design Review, and 18.40 ­ Use Classifications.

9. AGENDA SETTING
Items discussed in this Agenda Setting Section will be considered by the Council for placing on a future agenda. No action will be taken on these items at this meeting.

10. PUBLIC COMMENT
Persons wishing to address the City Council on matters NOT on the posted agenda may do so.

Each speaker is limited to two minutes. If there are more than five individuals wishing to speak during public comment, the Mayor may choose to allow the first five speakers to speak during this time, and the balance of the Public Comment speakers will be called upon at the end of the Council Meeting.

If the item you are speaking on is not listed on the agenda, please be advised that the City Council may briefly respond to statements made or questions posed as allowed under the Brown Act (Government Code Section 54954.2). The City Council's general policy is to refer items to staff for attention, or have a matter placed on a future City Council agenda for a more comprehensive action or report and formal public discussion and input at that time.

11. ADJOURNMENT
Any writings or documents provided to a majority of the City Council regarding any item on this agenda will be made available for public inspection upon request.

In compliance with the Americans with Disabilities Act and Title VI, and as outlined in the City’s Reasonable Accommodations Policy, if you need special assistance or translation services to participate in this meeting, please contact the City Clerk’s Office at (650) 802­4222 or via email at [email protected]. Notification in advance of the meeting will enable the City to make reasonable arrangements to ensure accessibility to this meeting. 3 11. ADJOURNMENT
Any writings or documents provided to a majority of the City Council regarding any item on this agenda will be made available for public inspection upon request.

In compliance with the Americans with Disabilities Act and Title VI, and as outlined in the City’s Reasonable Accommodations Policy, if you need special assistance or translation services to participate in this meeting, please contact the City Clerk’s Office at (650) 802­4222 or via email at [email protected]. Notification in advance of the meeting will enable the City to make reasonable arrangements to ensure accessibility to this meeting. 4 San Carlos City Council/Successor Agency to the
Redevelopment Agency/Housing Authority Regular Meeting
Council Chambers, City Hall
600 Elm Street, San Carlos, CA 94070
September 11, 2023 7:00 PM

MINUTES

ROLL CALL
City Council Present:

City Council Absent:

Adam Rak, Mayor
John Dugan, Vice Mayor
Sara McDowell, Councilmember (Remote Pursuant to AB 2449) Pranita Venkatesh, Councilmember
Ronald Collins, Councilmember
Staff Present: Nil Blackburn, Assistant City Manager
Emma Licko, Recreation Coordinator
Steven Machida, Public Works Director
Jeff Maltbie, City Manager
Rebecca Mendenhall, Administrative Services Director
Lauren Schneider, Recreation Coordinator
Tyler Muela, Recreation Manager
Crystal Mui, City Clerk
Amy Newby, Parks and Recreation Director
Gregory Rubens, City Attorney
Wendy Schettino, Recreation Supervisor

1. CALL TO ORDER
Mayor Rak called the meeting to order at 7:00 PM.

2. ASSEMBLY BILL 2449 TELECONFERENCE REQUESTS
Mayor Rak announced that Councilmember McDowell will be joining the meeting remotely pursuant to Assembly Bill (AB) 2449’s just cause provision.

Councilmember McDowell provided a general description of her circumstances.

Mayor Rak announced that Councilmember Collins is absent from tonight’s meeting.

City Clerk Crystal Mui provided information validating the City’s compliance with AB 2449.

3. PLEDGE OF ALLEGIANCE
Mayor Rak requested a moment of silence to pay tribute to victims of the September 11, 2001 terrorist attacks.

May Rak led the Pledge of Allegiance.

7.b
October 23, 2023 Packet Pg. 5

4. CHANGES TO THE ORDER OF THE AGENDA
None.

5. REPORT FROM CLOSED SESSION
City Attorney Greg Rubens stated that there are no reports from the Closed Session items held this evening at the 6:30 PM Special Council Meeting.

6. PRESENTATIONS
a. Present a Proclamation Congratulating the San Carlos United Soccer Club’s U17 Women’s Team Upon Winning the Elite Clubs National League (ECNL) Women’s Regional League Championship.

Mayor Rak presented a proclamation to the U17 Women’s Team congratulating them for winning the Elite Clubs National League Championship.

U17 Captains Emma Heist and Ryann Leyete-Vidal expressed pride in their team for their dedication and efforts. They thanked Council for the recognition and U17 Coach Nick Dye and their parents for their support.
b. Present a Proclamation Recognizing September 2023 as Suicide Prevention Month.

Mayor Rak recognized September 2023 as Suicide Prevention Month. San Mateo County Behavioral Health Commission’s Youth Action Boardmember Rhea Nandel accepted the proclamation on behalf of her Commission and encouraged the community to promote this year’s theme - Share Hope Together.

Councilmember McDowell announced an upcoming suicide prevention workshop at the library and encouraged the community to sign-up.

Mayor Rak recognized Councilmember McDowell for her work with the Mayors Mental Health Initiative last year.
c. Present a Proclamation Recognizing September 2023 as Recovery Happens Month.

Mayor Rak recognized September 2023 as Recovery Happens Month. Heather Henry of Voices of Recovery San Mateo County received the proclamation, thanked Council for the recognition and spoke on the importance of raising awareness of recoveries and transformed lives.
d. Receive a Presentation from CORA (Community Overcoming Relationship Abuse) on Their Speak Up Campaign.

Mayor Rak provided background on the City of San Carlos’ partnership with CORA (Community Overcoming Relationship Abuse) to create the Speak Up pilot program and welcomed CORA CEO Dr. Karen Ferguson to speak on the campaign’s initial work of engaging and educating the community and businesses.

Councilmember McDowell spoke on the program and thanked CORA for their partnership.

7.b
October 23, 2023 Packet Pg. 6

7. COUNCIL COMMUNICATIONS AND ANNOUNCEMENTS
Mayor Rak announced that he attended the ribbon cutting for Molly O’s Irish Pub and Restaurant, presented a 100th birthday proclamation to Tillie, and provided City updates to the residents at San Carlos Elms.

8. PUBLIC COMMENT
Sonia Elkes, resident, requested that Council continue to prioritize and look for funding to proceed with the pedestrian bridge and Holly 101 interchange project.

9. CONSENT CALENDAR
MOTION: Approve City Council Consent Calendar Items ‘a’ through ‘i’.

MOVER: John Dugan
SECONDER: Pranita Venkatesh
AYES: McDowell, Venkatesh Dugan, Rak
NAYS: None.

ABSENT: Collins
RESULT: Motion Passed 4 – 0 – 1
a. Motion to Waive Reading of All Ordinances.
b. Approve the August 14, 2023 City Council Special Meeting Minutes. c. Approve the August 14, 2023 City Council Regular Meeting Minutes. d. Authorize Cancellation of the December 25, 2023 City Council Meeting. e. Adopt a Resolution Approving the 2024 Sewer System Root Foaming Project C1752 Specifications and Authorizing a Call for Bids. Resolution 2023-109 f. Adopt a Resolution Approving the 2024 Citywide Sidewalk Repair Project C9465 Specifications and Authorizing a Call for Bids. Resolution 2023-110
g. Deny Claim of Andy Ravella.
h. Deny Claim of Francesco Ruggiero.
i. Deny Claim of Geoffroy Raby.

10. NEW BUSINESS
a. Consideration of Appointing One Youth Advisory Council (YAC) Voting Member for the 2023 – 2024 Term, Two Alternate YAC Members for the 2023 – 2024 Term, and Five YAC Voting Members for the 2023 – 2025 Term, and Recognizing Retiring YAC Members.

Parks and Recreation Director Amy Newby commenced the item by thanking Councilmember Collins for assisting in this year’s Youth Advisory Council (YAC) member interviews and turned the presentation over to Recreation Coordinator Emma Licko. Ms. Licko introduced the proposed YAC members and recognized the retiring members.

7.b
October 23, 2023 Packet Pg. 7
Vice Mayor Dugan commended the past, present and future YAC members for their involvement in the community.

MOTION: Appoint the Following to the Youth Advisory Council: Samina Ginwalla as a Voting Member to the 2023-2024 Term; Maya Kacholiya and Michael Sandoval as Alternate Members to the 2023-2024 Term; and Sufiya Kaul, Connor Huh, Dylan Karmin, Cecily Mock and Zuri Kadiwar as Voting Members to the 2023-2025 Term; and Recognize Retiring Youth Advisory Council Members.

MOVER: Pranita Venkatesh
SECONDER: John Dugan
AYES: Dugan, McDowell, Venkatesh, Rak
NAYS: None.

ABSENT: Collins
RESULT: Motion Passed 4 – 0 – 1
City Clerk Crystal Mui administered the Oath of Office to the newly appointed YAC members. b. Consideration of the Formation of the City Centennial Advisory Committee and Direct Staff to Proceed with Recruitment.

Parks and Recreation Director Amy Newby presented on the proposed City Centennial Advisory Committee and responded to Council questions.

MOTION: Direct Staff to Proceed with the Recruitment for the City Centennial Advisory Committee and add seats for the residing Mayor and Vice Mayor and increase the community members/residents from three to five seats in total.

MOVER: John Dugan
SECONDER: Pranita Venkatesh
AYES: Venkatesh, Dugan, McDowell, Rak
NAYS: None.

ABSENT: Collins
RESULT: Motion Passed 4 – 0 – 1
c. Consideration of Adopting a Resolution Adopting a Memorandum of Understanding Between the City of San Carlos and the Local 829 American Federation of State, County and Municipal Employees ("AFSCME") for the Period of July 1, 2023 through June 30, 2026.

Administrative Services Director Rebecca Mendenhall presented the proposed amendments to the Memorandum of Understanding for the Local 829 American Federation of State, County and Municipal Employees (AFSCME) and the Management and Confidential Groups’ Salary and Benefit Resolutions, and responded to Council questions.

Vice Mayor Dugan expressed appreciation to all City employees for their hard work during the COVID pandemic.

MOTION: Adopt Resolution 2023-111 Adopting a Memorandum of Understanding Between the City of San Carlos and the Local 829 American Federation of State, County and Municipal Employees ("AFSCME") for the Period of July 1, 2023 through June 30, 2026.

MOVER: Pranita Venkatesh

7.b
October 23, 2023 Packet Pg. 8
SECONDER: John Dugan
AYES: McDowell, Venkatesh, Dugan, Rak
NAYS: None.

ABSENT: Collins
RESULT: Motion Passed 4 – 0 – 1
d. Consideration of Adopting a Resolution Adopting the Amended Salary and Benefit Resolution for the Management Group for the Period July 1, 2023 through June 30, 2026.

Administrative Services Director Rebecca Mendenhall presented the proposed Management Group’s Salary and Benefit Resolution under item 10c.

Before the vote was taken, City Attorney Greg Rubens announced that the salary increase percentage applied to employees of the Management Group would also apply to some other city executives as defined under the California Government Code.

MOTION: Adopt Resolution 2023-112 Adopting the Amended Salary and Benefit Resolution for the Management Group for the Period July 1, 2023 through June 30, 2026.

MOVER: John Dugan
SECONDER: Pranita Venkatesh
AYES: McDowell, Venkatesh, Dugan, Rak
NAYS: None.

ABSENT: Collins
RESULT: Motion Passed 4 – 0 – 1
e. Consideration of Adopting a Resolution Adopting the Amended Salary and Benefit Resolution for the Confidential Group for the Period July 1, 2023 through June 30, 2026.

Administrative Services Director Rebecca Mendenhall presented the proposed Confidential Group’s Salary and Benefit Resolution under item 10c.

MOTION: Adopt Resolution 2023-113 Adopting the Amended Salary and Benefit Resolution for the Confidential Group for the Period July 1, 2023 through June 30, 2026.

MOVER: Pranita Venkatesh
SECONDER: John Dugan
AYES: Dugan, McDowell, Venkatesh, Rak
NAYS: None.

ABSENT: Collins
RESULT: Motion Passed 4 – 0 – 1

11. PUBLIC HEARING
a. Consideration of Introducing an Ordinance Amending and Replacing San Carlos Municipal Code Chapter 8.07 - Tobacco Retailer Permits, to Consolidate and Clarify Existing Definitions and Enact Additional Requirements for Tobacco Retailer Permits to Align with the County of San Mateo Model Ordinance.

7.b
October 23, 2023 Packet Pg. 9
City Attorney Greg Rubens presented on the item and spoke on the need to amend the City’s Municipal Code on Tobacco Retailer Permits. Mr. Rubens and City Manager Jeff Maltbie responded to Council questions.

Public Comment
- Edward Schlessinger, resident and member with Smoke Free San Carlos and San Mateo County Tobacco Education Coalition, spoke in support of the Ordinance. - Tricia Barr, resident and Co-Chair of the San Mateo County Tobacco Education Coalition, thanked Council for considering the Ordinance and spoke in support of it.

MOTION: Approve to Close the Public Hearing.

MOVER: John Dugan
SECONDER: Pranita Venkatesh
AYES: Venkatesh, Dugan, McDowell, Rak
NAYS: None.

ABSENT: Collins
RESULT: Motion Passed 4 – 0 – 1
MOTION: Introduce Ordinance 1600 Amending and Replacing San Carlos Municipal Code Chapter 8.07 - Tobacco Retailer Permits, to Consolidate and Clarify Existing Definitions and Enact Additional Requirements for Tobacco Retailer Permits to Align with the County of San Mateo Model Ordinance.

MOVER: John Dugan
SECONDER: Pranita Venkatesh
AYES: McDowell, Venkatesh, Dugan, Rak
NAYS: None.

ABSENT: Collins
RESULT: Motion Passed 4 – 0 – 1

12. AGENDA SETTING
a. Consideration of Agendizing an Item to Rezone and Change the Land Use Designation of San Carlos Owned Public Open Space that’s Contiguous to San Carlos City Parks as Park Land.

Mayor Rak suggested that the City transfer open space areas that are contiguous to park land and provide additional protections.

Council voiced support to adding the item on a future agenda for consideration.

13. ADJOURNMENT
Mayor Rak adjourned the meeting at 8:24 PM in Memory of Karina Castro and offered condolences to her family.

Crystal Mui,
City Clerk

7.b
October 23, 2023 Packet Pg. 10

CITY COUNCIL

STAFF REPORT
MEETING DATE: October 23, 2023
ITEM TITLE: Adopt a Resolution Awarding the 2024 Sewer System Root Foaming Project C1752; Authorizing the City Manager to Execute a Public Projects Agreement with Duke’s Root Control, Inc. of Elgin, Illinois in the Amount of $150,678.45; and Authorizing the Expenditure of Contingency up to the Project Budget.

RECOMMENDATION:

Staff recommends that the City Council adopt a Resolution awarding the 2024 Sewer System Root Foaming Project C1752 (“Project”); authorizing the City Manager to execute a public projects agreement with Duke’s Root Control, Inc. of Elgin, Illinois in the amount of $150,678.45; and authorizing the expenditure of contingency up to the Project budget.

FISCAL IMPLICATIONS:

There are no fiscal impacts and no additional appropriations are needed at this time.

Funding for the Project comes from C1752 which has an available budget of $174,765 for fiscal year 2023-24. There is sufficient budget to award the Project for the total bid amount of $150,678.45 and contingency up to the Project budget.

BACKGROUND:

In the past, the City’s maintenance staff managed the root control program on an as-needed basis. The City’s engineering staff now manages the root control program to address the large number of sewer mains with root intrusion and to coordinate repairs with the future annual sewer rehabilitation projects.

Sewer line rehabilitation and replacement are still the City’s primary means of repairing sewer line defects, but the use of chemical root control can be effective in reducing and preventing root defects until the complete repair or replacement of the pipe is scheduled. Root intrusion inside sanitary sewer mains is a significant cause of sanitary sewer overflows (SSOs) in San Carlos, causing approximately 25 to 30 percent of SSOs annually.

Root foaming efforts help to minimize and prevent SSOs in the sewer system. Prioritization of sewer lines is determined by the specific sewer basin, the number of root defects as identified by closed circuit television inspections, and the number of blockages caused by roots as indicated by maintenance history and maintenance staff.

The chemical used for root treatment has been approved by the Environmental Protection Agency (EPA) and Silicon Valley Clean Water. In addition, the chemical is non-toxic and does not require

7.c
October 23, 2023 Packet Pg. 11
the removal of trees, nor does it impair the health of the trees.

ANALYSIS:

For the Project, staff identified Basin 16 for root control treatment due to its maintenance history.

The City Engineer signed the final bid set construction documents on August 14, 2023, and the City Council approved the construction documents at its September 11, 2023 meeting.

On September 12, 2023, the City advertised for bids for construction of the Project and bids were opened on October 3, 2023. One bid was received with the following results:

Contractor Bid Amount
Engineer’s Estimate $126,829.50
Duke’s Root Control, Inc $150,678.45
The lowest responsible and responsive bid was submitted by Duke’s Root Control, Inc. in the amount of $150,678.45. After bid evaluation, staff recommends awarding the contract to Duke’s Root Control, Inc. The receipt of only one bid is attributed to the City’s requirement of a non-toxic and EPA approved chemical agent for treatment.

ALTERNATIVES:

The alternatives available to the City Council include:

1. Adopt a Resolution awarding the 2024 Sewer System Root Foaming Project C1752; authorizing the City Manager to execute a public projects agreement with Duke’s Root Control, Inc. of Elgin, Illinois in the amount of $150,678.45; and authorizing the expenditure of a contingency up to the Project budget; or

2. Do not adopt the Resolution; or

3. Provide staff with alternative direction.

Respectfully submitted by:

Steven Machida, Public Works Director
Approved for submission by:
_______________________
Jeff Maltbie, City Manager
ATTACHMENT(S):

1. Resolution

7.c
October 23, 2023 Packet Pg. 12
RESOLUTION NO. 2023 – ____

A RESOLUTION OF THE CITY COUNCIL OF THE CITY OF SAN CARLOS AWARDING THE 2024 SEWER SYSTEM ROOT FOAMING PROJECT C1752;

AUTHORIZING THE CITY MANAGER TO EXECUTE A PUBLIC PROJECTS AGREEMENT WITH DUKE’S ROOT CONTROL, INC. OF ELGIN, ILLINOIS IN THE AMOUNT OF $150,678.45; AND AUTHORIZING THE EXPENDITURE OF CONTINGENCY UP TO THE PROJECT BUDGET.

WHEREAS, in the past, the City's maintenance staff managed the root control program on an as-needed basis; and
WHEREAS, to address the large number of sewer mains with root intrusion and to coordinate repairs with the future annual sewer rehabilitation projects, the City's engineering staff now manages the root control program; and
WHEREAS, though sewer line rehabilitation and replacement are still the City's primary means of repairing sewer line defects, the use of chemical root control can be effective in reducing and preventing root defects until the complete repair or replacement of the pipe is scheduled; and WHEREAS, root intrusion inside sanitary sewer mains is a significant cause of sanitary sewer overflows (SSOs) in San Carlos, causing approximately 25 to 30 percent of SSOs annually; and WHEREAS, root foaming efforts help to minimize and prevent SSOs in the sewer system; and
WHEREAS, the chemical used for root treatment is non-toxic, does not require the removal trees nor does it impair the health of the trees, and has been approved by the Environmental Protection Agency and Silicon Valley Clean Water; and
WHEREAS, the City Engineer signed the final bid set construction documents on August 14, 2023, and the City Council approved the construction documents at its September 11, 2023, meeting; and
WHEREAS, on September 12, 2023, the City advertised for bids for construction of the 2024 Sewer System Root Foaming Project (“Project”) and bids were opened on October 3, 2023; and WHEREAS, the lowest responsible and responsive bid was submitted by Duke’s Root Control, Inc. in the amount of $150,678.45 and the receipt of only one bid is attributed to the City’s requirement for a non-toxic and EPA approved chemical agent for treatment.

NOW, THEREFORE BE IT RESOLVED, that the San Carlos City Council hereby awards the 2024 Sewer System Root Foaming Project C1752; authorizes the City Manager to execute a public projects agreement with Duke’s Root Control, Inc. of Elgin, Illinois in the amount of $150,678.45; and authorizes the expenditure of contingency up to the Project budget. * * * * *

7.c
October 23, 2023 Packet Pg. 13
I, City Clerk Crystal Mui, hereby certify that the foregoing Resolution was duly and regularly passed and adopted by the City Council of the City of San Carlos at a scheduled meeting thereof held on the 23rd day of October 2023, by the following vote:

AYES, COUNCILMEMBERS: ___________________________________________ NOES, COUNCILMEMBERS: ___________________________________________ ABSENT, COUNCILMEMBERS: ___________________________________________ ________________________________
CITY CLERK of the City of San Carlos
APPROVED:
___________________________
MAYOR of the City of San Carlos

7.c
October 23, 2023 Packet Pg. 14

CITY COUNCIL

STAFF REPORT
MEETING DATE: October 23, 2023
ITEM TITLE: Adopt a Resolution Adopting a Meeting Decorum and Civility Policy for Public Meetings.

RECOMMENDATION:

Staff recommends that the City Council adopt a Resolution adopting a meeting decorum and civility policy.

Based on recent events, the City Council should consider and develop policies authorized under the Brown Act at Sections 54954.3, 54957.9, and 54957.95. This will provide guidance for the Mayor and Chairs of City Brown Act bodies should disruptive behavior occur at meetings and would operate to establish reasonable standards to protect the public’s rights to address the City Council and commissions should further disruptive behavior incidents occur.

Attachment 1 is a proposed Decorum and Civility Policy. It was developed through a review of state law and other agency policies. The draft policy is intended to be comprehensive in dealing with disruptive behaviors and is not specific to video conferenced meetings that use technology such as Zoom.

FISCAL IMPLICATIONS:

There are no fiscal implications associated with the recommended action.

BACKGROUND:

Government Code Section 54954.3(a) provides that unless an exception applies, every agenda for regular and special meetings of the City Council, Commissions and Standing Committees must provide an opportunity for members of the public to directly address the legislative body on any item of interest to the public, before or during the legislative body’s consideration of the item, that is within the subject matter jurisdiction of the legislative body.

Section 54954.3(b) provides that the City Council may adopt reasonable regulations to ensure public participation, including, but not limited to, regulations limiting the total amount of time allocated for public testimony on particular issues and for each individual speaker.

The Brown Act provides that the City Council is not allowed to prohibit public criticism of the policies, procedures, programs, or services of the agency, or of the acts or omissions of the legislative body. (Government Code Section 53954.3(c)). The Brown Act recognizes a general exception intended to cover first amendment issues providing that this section does not confer any privilege or protection for expression beyond that otherwise provided by law.

7.d
October 23, 2023 Packet Pg. 15
Government Code Section 54957.9 provides that in the event that any meeting is willfully interrupted by a group or groups of persons so as to render the orderly conduct of such meeting unfeasible and order cannot be restored by the removal of individuals who are willfully interrupting the meeting, the members of the legislative body conducting the meeting may order the meeting room cleared and continue in session. If such a room clearing is ordered, only matters appearing on the agenda may be considered in such a session. Representatives of the press or other news media, except those participating in the disturbance, are allowed to attend such a cleared session.

The City Council is allowed to establish a procedure for readmitting an individual or individuals not responsible for willfully disturbing the orderly conduct of the meeting.

Government Code Section 54957.95, which became effective on January 1, 2023, provides that in addition to the provisions Sections 54954.3 and 54957.9, the Mayor or official presiding over or conducting a meeting or their designee may remove, or cause the removal of, an individual for behavior disrupting the meeting.

Under this law, prior to removing an individual, the presiding member or their designee must first warn the individual that their behavior is disrupting the meeting and that their failure to cease their behavior may result in their removal. The presiding member or their designee may then remove the individual if they do not promptly cease their disruptive behavior. This limitation does not prevent removal of a person or persons making a “true threat of force” as defined in the statute.

ANALYSIS:

The mayor as presiding officer has discretion to control the conduct of the meeting, balancing the public’s free speech rights with the body’s ability to consider and deliberate without being thwarted through disruptive behavior. A city council meeting is a limited public forum, allowing reasonable limitations on speech to allow the body to conduct business. Consistent with this, the Brown Act allows both the establishment of reasonable regulations to ensure public participation in Section 54954.3, and addresses how to readmit members of the public after a disruption. Reasonable policy guidance will provide the mayor or presiding officer an opportunity to warn and to point to a policy violation in managing a meeting and disruptive behavior.

The law allows the presiding officer to limit discussion to the issues at hand and to those matters under the jurisdiction of the City.

The City has some rules for the conduct of meetings. Roberts Rules of Order provide guidance on parliamentary procedures. The City limits speakers to two minutes and there is an initial time limitation on the general public comment period.

The City currently has no written policies on the conduct of meetings to address intentional disruptions and removal, other than as generally provided in state law and historical practice.

The ”Zoom Bombers” plaguing Bay Area and California cities appear to be coordinating their behavior to disrupt meetings, disguising themselves as concerned citizens, only to launch into obscene and offensive behaviors, not relevant or pertinent to the item under discussion, and intended to cause disruption to the meetings. Disruption includes shocking the members of the legislative or other Brown Act bodies and the public in attendance. The use of Zoom for public comment creates challenges in controlling disruptive behavior during public meetings since persons on Zoom can be anonymous. Zoom participation can be from anywhere in the world and persons from outside of San Carlos and the state. As such, those intending to disrupt a meeting are not subject to California or local jurisdiction. Removal after an intentional disruption can be

7.d
October 23, 2023 Packet Pg. 16
accomplished with the click of a button, but must still comply with the Brown Act rules for public participation.

ALTERNATIVES:

The alternatives available to the City Council include:

1. Adopt a Resolution adopting a meeting decorum and civility policy for public meetings; or

2. Do not adopt the meeting decorum policy; or

3. Provide staff with alternative direction.

Respectfully submitted by:

Gregory Rubens, City Attorney
Approved for submission by:
_______________________
Jeff Maltbie, City Manager
ATTACHMENT(S):

1. Resolution
Exhibit A to Resolution - Meeting Decorum and Civility Policy

7.d
October 23, 2023 Packet Pg. 17
RESOLUTION NO. 2023-____

A RESOLUTION OF THE CITY COUNCIL OF THE CITY OF SAN CARLOS

ADOPTING A MEETING DECORUM AND CIVILITY POLICY FOR PUBLIC MEETINGS ____________________________________________________________________________ WHEREAS, across the nation many Cities have adopted policies and rules to establish decorum and enhance civility at public meetings, including the United States Conference of Mayors, which adopted a Civility Accord; and
WHEREAS, Government Code Sections 54954.3, 54957.9 and 54957.95 provide that the City Council may adopt reasonable regulations to ensure public participation, including, but not limited to, regulations limiting the total amount of time allocated for public testimony on particular issues and for each individual speaker, a procedure for readmitting persons after a meeting is cleared and to provide for removal of persons whose behavior is disrupting a meeting; and WHEREAS, the City of San Carlos has a strong commitment to the democratic process, individual rights of expression, robust debate, and tolerance for disparate views, with such expression and debate conducted in a civil manner; and
WHEREAS, the San Carlos City Council, the City's boards and commissions, other public bodies, citizens, interested persons and various community groups participate in public meetings, which at times entail consideration of controversial issues that may engender passionate and often conflicting opinions; and
WHEREAS, intentional behavior designed to disrupt a meeting, impropriety, incivility, and disrespect at these public meetings can stifle participation and debate, threaten the quality of decisions, and undermine the local democratic process; and WHEREAS, adopting rules of decorum and civility applicable to all public meetings will ensure that civic engagement and local democracy continue to flourish in San Carlos; and WHEREAS, appropriate and reasonable rules of decorum and civility will enable the Mayor and presiding officer to conduct an orderly meeting, while respecting participation of the public.

NOW, THEREFORE, BE IT RESOLVED that the City Council of the City of San Carlos hereby adopts the attached Decorum and Civility Policy for the conduct of Public meetings. * * * * *
I, City Clerk Crystal Mui, hereby certify that the foregoing Resolution was duly and regularly passed and adopted by the City Council of the City of San Carlos at a scheduled meeting thereof held on the 23rd day of October 2023, by the following vote:

AYES, COUNCILMEMBERS: ______________________________________________ NOES, COUNCILMEMBERS: ______________________________________________ ABSENT, COUNCILMEMBERS: ______________________________________________

7.d
October 23, 2023 Packet Pg. 18
________________________________
CITY CLERK of the City of San Carlos
APPROVED:
__________________________________
MAYOR of the City of San Carlos
Exhibit A: Meeting Decorum and Civility Policy

7.d
October 23, 2023 Packet Pg. 19

RULES OF DECORUM AND CIVILITY AT PUBLIC MEETINGS
The City of San Carlos is determined to provide safe, open, and fair access to all persons wishing to participate in its local public meetings (“Public Meetings”) while ensuring that Public Meetings are not disrupted or impeded by behavior that violates City policies.

The City Council hereby establishes the following reasonable and lawful regulations:

The Council rules of procedure shall be Roberts Rules of Order.

Time Limitations on addressing the Council, Commissions, or Brown Act Committees The time limit for individual public comment shall be two minutes per agenda item, which may be reduced at the discretion of the Mayor or the Chair of the City body (hereinafter "Presiding Officer") when more than ten persons are requesting to speak to an item on the agenda to allow more participants time to speak to an item.

The Presiding Officer, in order to provide for efficient use of public comment time at the meeting, may grant additional time for groups of persons who agree to pool their time to allow one speaker to present on their behalf on an agenda item up to a maximum of ten minutes.

For general public comment, on matters not on the posted agenda, the first five speakers will be allowed to speak. After the first five speakers the balance of public comment will occur at the end of the meeting, unless the Presiding Officer determines that the remaining public comment can be completed in a reasonable time.

The total time for public comment on any item may be set at the beginning of an agenda item by a vote of the council, board, or commission or as stated on the Agenda. Where a time limit for public comment is not set, the Presiding Officer may also conclude public comment on an item by announcing a last opportunity for members to indicate their intention to speak to an agenda item.

RULES OF DECORUM AND CIVILITY POLICY
Consistent with Government Code Sections 54957.3 and 54957.95 persons attending a Public Meeting covered under the Brown Act shall not engage in behavior during such a meeting that actually disrupts, disturbs, impedes, or renders infeasible the orderly conduct of a meeting.

All persons attending a Public Meeting are expected to adhere to the following standards of conduct:
• Treat everyone courteously.
• Listen to City Officials and other members of the public respectfully. • Exercise self-control and avoid threats of violence and loud, insulting, demeaning, or offensive communications.
• Give open-minded consideration to all viewpoints.
• Focus on the issues and avoid personalizing debate.
• Allow all members of the public to speak without intimidation or interruption; and • Embrace respectful disagreement and dissent as democratic rights that are inherent components of an inclusive public process and tools for forging sound decisions.

7.d
October 23, 2023 Packet Pg. 20
In furtherance of the foregoing standards of conduct, the rules of decorum set forth below shall be followed:
• No person attending a Public Meeting shall engage in disorderly or boisterous conduct, including, but not limited to, whistling, stamping of feet, booing, or making any loud, threatening, profane, abusive, personal, impertinent, or slanderous utterance, that disturbs, disrupts, or otherwise impedes the orderly conduct of the meeting. • No person attending a Public Meeting shall speak for longer that their allotted time, in accordance with the time limits set forth above, without permission of the Presiding Officer. • All remarks by members of the public shall be addressed to the Presiding Officer and not to any other member of the public or to any individual member of the City body unless in response to a question from that member.
• No person attending a Public Meeting shall engage in behavior that may interfere with the rights of other speakers.
• All persons attending a Public Meeting shall listen courteously and attentively to all public discussions at the meeting and avoid interrupting members of the public addressing the City body or City Officials.
• Signs, placards, banners, or other similar items shall not be permitted in the audience during a public meeting if the Presiding Officer determines that the presence of such items disturbs, disrupts, or otherwise impedes the orderly conduct of the meeting or the ability of members of the public to view presentations.
• Members of the public while attending a Public Meeting shall refrain from abusive conduct, or verbal attacks upon the character of City Officials. • All persons attending a Public Meeting shall obey any lawful order of the Presiding Officer to enforce the Rules of Decorum.
• It is the responsibility of the Presiding Officer to keep comments on topic during Public Meetings. Individuals should honor efforts by the Presiding Officer to focus discussion pertinent to the agenda item at hand and within the jurisdiction of the Council or Commission.
• All persons attending a Public Meeting shall not engage in behavior that constitutes a true threat of force as defined in Government Code 54957.95(b)(2).

Enforcement of Rules and Decorum and Civility Policy
The Presiding Officer shall be responsible for maintaining the decorum and civility at Public Meetings and enforcing the Rules of Decorum in a uniform and even-handed manner, as follows:
• In the event that an attendee of the Public Meeting breaches the Rules of Decorum and Civility in a manner that disturbs, disrupts, or otherwise impedes the orderly conduct of a Public Meeting, the Presiding Officer shall provide an oral warning ordering that person to cease the offending conduct.
• If a member of the public does not improve his or her behavior in response to the verbal warning, the Presiding Officer may order the abusive individual or individuals to leave the premises for a short period of time (e.g., the remainder of the day). • If a member of the Public makes a true threat of force as defined in Government Code 54957.95(b)(2), he or she may be removed from the meeting without a warning. • The Presiding Officer may, but is not required to, call a recess at any time for a cooling off period or to adjourn the meeting before taking any specific action to remove individuals whose behavior is disrupting, disturbing, impeding or otherwise rendering the orderly conduct of a meeting infeasible.

7.d
October 23, 2023 Packet Pg. 21
• In the event that any meeting is willfully interrupted by a group or groups of persons so as to render the orderly conduct of such meeting unfeasible and order cannot be restored by the removal of individuals who are willfully interrupting the meeting, the members of the legislative body conducting the meeting may order the meeting room cleared and continue in session. If such a room clearing is ordered, only matters appearing on the agenda may be considered in such a session. Representatives of the press or other news media, except those participating in the disturbance, are allowed to attend the cleared session. If after the room clearing, the Presiding Officer in consultation with City Staff or law enforcement believes the orderly conduct of the meeting can resume without the attendees who willfully disrupted the meeting, the legislative body by motion may vote to readmit those who did not willfully disrupt the meeting. • The Presiding Officer may engage the efforts of law enforcement as necessary to carry out lawful removal orders.
• The Presiding Officer may intervene to ensure that the Code of Conduct and Ethics Policy for Elected and Appointed Officials rules for conduct at meetings is followed. • The above-described remedies for compliance with the Rules of Decorum and Civility are not exclusive and shall not preclude the application or use of other remedies provided by State law or the Municipal Code.
• A breach of the Rules of Decorum and Civility Policy shall in no event be a basis for the invalidation of any action taken by the City Council or any City board, commission, or committee.

7.d
October 23, 2023 Packet Pg. 22

CITY COUNCIL

STAFF REPORT
MEETING DATE: October 23, 2023
ITEM TITLE: Adopt Ordinance 1601 Approving the 841 Old County Road Project Planned Development Plan and Related Zoning Map Amendment to Rezone the Project Site from Heavy Industrial (IH) to Planned Development (PD) at 841 Old County Road (APNs 046-133-160, 046- 134-050, 046-134-060, 046-135-010, 046-135-020, 046-135-030, 046- 135-040, 046-182-100, 046-182-110, 046-182-150).

RECOMMENDATION:

The Planning and Transportation Commission and staff recommend that the City Council adopt Ordinance 1601 approving the 841 Old County Road Project (“Project”) Planned Development Plan and related Zoning Map amendment to rezone the Project Site from Heavy Industrial (IH) to Planned Development (PD) at 841 Old County Road (APNs 046-133-160, 046-134-050, 046-134- 060, 046-135-010, 046-135-020, 046-135-030, 046-135-040, 046-182-100, 046-182-110, 046- 182-150).

FISCAL IMPLICATIONS:

The Applicant has paid the appropriate application fees and provided deposit funds to pay for expenses related to the environmental review and other reports and analyses associated with the Project. The Project will be required to pay building permit fees and City impact fees. City impact fees total over $12.9 million and include commercial linkage (affordable housing), childcare, sewer and traffic fees. The development agreement includes community benefits, which are valued at $7.69 million.

The proposed development will also benefit the City with increased property tax, increased sales tax revenue, and new job creation. The estimated increased revenue to the City is $13.6 million over 20 years.

BACKGROUND:

The Planning and Transportation Commission, at its June 7, 2023 meeting conducted a public hearing and adopted Resolution PTC2023-11, recommending the City Council adopt the Mitigated Negative Declaration and associated Mitigation Monitoring and Reporting Program and adopted Resolution PTC2023-12 recommending the City Council adopt the Ordinance to zone the site Planned Development (PD) Zoning, approve the associated Planned Development Plan, and adopt the Ordinance approving the development agreement. The Planning and Transportation Commission also approved the Design Review, Tentative Parcel Map, Transportation Demand Management Plan, and Grading and Dirt Haul Certificate subject to the approval of the Planned Development zoning.

7.e
October 23, 2023 Packet Pg. 23
The City Council heard the item at its August 28, 2023 meeting and continued the hearing, requesting that the developer expand its community benefit offer. At its October 9, 2023 meeting, the City Council conducted the public hearing and adopted Resolution 2023-125 approving the Mitigated Negative Declaration and Mitigation Monitoring and Reporting Plan, introduced Ordinance 1601 to rezone the site from Heavy Industrial (IH) to Planned Development Zoning and approving the Planned Development Plan, and introduced Ordinance 1602 approving the development agreement as revised at the meeting.

ANALYSIS:

The Planned Development Ordinance authorizes a two new research and development buildings with underground parking at 841 Old County Road with the following development standards:

1. Height: Exceed the maximum height of 50’ allowed the IH District. The applicant proposes the two new buildings, a four-story building at a height of 74’-6” to the roof parapet and 83’ to the top of the mechanical screen and a five story building at a height of 90’-6” to the top of the roof parapet and 99’ to the top of the mechanical screen.

2. Floor Area: Exceed the maximum site floor area ratio of 1.0. The applicant proposes total building square footage at 339,170 square feet resulting in a FAR of 2.28.

3. Setback: Reduce exterior side yard setback on the Commercial Street side from 5’ to 2’- 6” to accommodate street widening.

4. Use: All uses as allowed in the Heaving Industrial zoning district. All future tenants will be required to comply with the biosafety regulations in effect at the time a business registration or building permit is issued for tenant lab space.

Environmental Review.

The City Council adopted Resolution 2023-125 approving the Mitigated Negative Declaration and Mitigation Monitoring Plan prepared in accordance with CEQA guidelines. With implementation of the mitigation measures, the project will not result in a significant impact to the environment.

ALTERNATIVES:

The alternatives available to the City Council include:

1. Adopt Ordinance 1601 approving the 841 Old County Road Project Planned Development Plan and related Zoning Map amendment to rezone the Project Site from Heavy Industrial (IH) to Planned Development (PD) at 841 Old County Road (APNs 046-133-160, 046-134- 050, 046-134-060, 046-135-010, 046-135-020, 046-135-030, 046-135-040, 046-182-100, 046-182-110, 046-182-150); or

2. Do not adopt the Ordinance; or

3. Provide staff with alternative direction.

Respectfully submitted by:

Al Savay, Community Development Director

7.e
October 23, 2023 Packet Pg. 24
Approved for submission by:
_______________________
Jeff Maltbie, City Manager
ATTACHMENT(S):

1. Ordinance 1601 with Exhibit A – Zoning Map
Exhibit B to Ordinance - Planned Development Plans
Exhibit C to Ordinance - Findings

7.e
October 23, 2023 Packet Pg. 25
4864-3640-1272 v2
ORDINANCE NO. 1601

AN ORDINANCE OF THE CITY OF SAN CARLOS APPROVING THE
841 OLD COUNTY ROAD PROJECT PLANNED DEVEOPMENT PLAN AND RELATED

ZONING MAP AMENDMENT TO REZONE THE PROJECT SITE FROM HEAVY INDUSTRIAL (IH) TO PLANNED DEVELOPMENT (PD) AT 841 OLD COUNTY ROAD (APN 046-133-160, 046-134-050, 046-134-060, 046-135-010, 046-135-020, 046-135-030, 046-135- 040, 046-182-100, 046-182-110, 046-182-150).

RECITALS
WHEREAS, pursuant to Title 18 of the City of San Carlos Municipal Code (the “Zoning Code”), SI 74, LLC, a California limited liability company filed an application for approval of a Planned Development Plan and accompanying Zoning Map Amendment for the development of the 841 Old County Road Project (APN 046-133-160, 046-134-050, 046-134-060, 046-135-010, 046-135-020, 046-135-030, 046-135-040, 046-182-100, 046-182-110, 046-182-150); and WHEREAS, SI 74, LLC, transferred title to the property to The Sobrato Family Foundation, a California nonprofit public benefit corporation. Both entities are controlled by members of the Sobrato family. The City has since updated the application to reflect that The Sobrato Family Foundation, a California nonprofit public benefit corporation is the applicant; WHEREAS, by Resolution PTC2023-11, adopted on June 7, 2023, the Planning and Transportation Commission recommends that the City Council adopt the Mitigated Negative Declaration and the Mitigation Monitoring and Reporting Plan pursuant to the California Environmental Quality Act (CEQA) for the implementation of the mitigation measures outlined in the Mitigated Negative Declaration; and
WHEREAS, at a duly noticed public hearing held on June 7, 2023, the Planning and Transportation Commission approved the Design Review Permit, Transportation Demand Management Plan, Grading and Dirt Haul Certificate, and Tentative Map; and WHEREAS, by Resolution PTC2023-12, adopted on June 7, 2023, the Planning and Transportation Commission recommends that the City Council approve the Zoning Map Amendment as set forth in Exhibit A to this Resolution and adopt the Planned Development (PD) Plan as set forth in Exhibit B to this Resolution; and
WHEREAS, the City Council of the City of San Carlos held duly noticed public hearings on August 28, 2023 and October 9, 2023 to consider the Mitigated Negative Declaration, Mitigation Monitoring and Reporting Plan, the proposed Planned Development Plan, and the proposed Zoning Map Amendment; and
WHEREAS, by Resolution 2023-__, adopted October 9, 2023, the City Council made findings and adopted the Mitigated Negative Declaration and Mitigation Monitoring and Reporting Plan pursuant to CEQA for the implementation of the mitigation measures outlined in the Mitigated Negative Declaration.

NOW, THEREFORE THE CITY COUNCIL OF THE CITY OF SAN CARLOS DOES HEREBY ORDAIN AS FOLLOWS:

7.e
October 23, 2023 Packet Pg. 26
4864-3640-1272 v2
SECTION 1: The Zoning Map Amendment of San Carlos is hereby amended from Heavy Industrial (IH) District to Planned Development (PD) District (Exhibit A), by the adoption of a Planned Development Plan for the construction of two research and development buildings with a total of 339,170 square feet above grade with one four story building at a height of 74’-6” to the roof parapet and 85’ to the top of the mechanical screen and a five story building at a height of 90’-6” to the roof parapet and 101’ to the top of the mechanical screen with below grade and atgrade parking and landscaping improvements on the 3.41 acre site located at 841 Old County Road (APNs 046-133-160, 046-134-050, 046-134-060, 046-135-010, 046-135-020, 046-135- 030, 046-135-040, 046-182-100, 046-182-110, 046-182-150) as shown on the plans prepared by Studios Architecture dated January 11, 2023 (Exhibit B).

SECTION 2: The City Council finds that the Planned Development Zone change and Plan of Development is consistent with the General Plan as described in Exhibit C.

SECTION 3: That the City Council hereby adopts the Plan of Development filed as “803- 851 Old County Road” attached hereto as Exhibit B. This plan indicates the location of the proposed building, the size of the building, the parking to be provided and areas to be landscaped.

Standards of Development are as follows:

1. The land use regulations for the PD zone shall be those uses allowed in the Heavy Industrial (IH) Zoning District. Research and Development Use shall be considered a Permitted Use. In addition, the following uses are permitted within the 1,500 square feet tenant space:
a. Instructional Services, Eating and Drinking Establishments (excluding night clubs), Animal Care, (excluding Veterinary Services), Personal Services (excluding Tattoo or Body Modification Parlor), Retail Sales (excluding Cannabis Dispensaries, Retail Establishments Selling Ammunition or Firearms), Sales and Services, Government Offices, and Cultural Institutions all as defined in Chapter 18.40 of the San Carlos Municipal Code.

2. Life Science/Research and Development tenants shall comply with the City’s Bio Safety regulations in effect at the time laboratory tenant improvements plans are submitted to the Building Department.

3. All tenants may only conduct activities classified as Biosafety Level 1 or 2 unless the City (including but not limited to any City agency, body, department, officer or employee) or its electorate (through the power of initiative or otherwise) adopts any ordinance, resolution, order, rule, official policy, standards, specifications, guidelines and/or other regulations (collectively, ‘New City Laws’) permitting activities classified as Biosafety Level Three or Biosafety Level Four and the tenant obtains all permits, approvals or other authorizations required by the New City Laws.

4. The buildings shall be situated on the property in accordance with the Plan of Development (attached hereto as Exhibit B) prepared by Studio Architecture, Inc. dated January 11, 2023. This plan indicates the location of the building, the size of the building, the parking to be provided and areas to be landscaped.

7.e
October 23, 2023 Packet Pg. 27
4864-3640-1272 v2

5. Floor area and height of the buildings shall be provided in substantial compliance with the Plan of Development. The project shall comply with the current zoning standards in effect except as follows:
i. The maximum building height is limited to 74’-6” to the top of the roof parapet and 83’ to the top of the mechanical screen for the four-story (north) building and 90’-6” to the top of the roof parapet and 99’ to the top of the mechanical screen for the five-story (south) building. ii. The total allowed floor area for the site is 339,170 square feet resulting in a FAR of 2.28.
iii. The exterior side yard setback along Commercial Street shall be 2’-6”.

6. The project shall be constructed in accordance with all requirements of the Mitigated Negative Declaration, Mitigation Monitoring & Reporting Plan, Design Review Certificate, Transportation Demand Management Plan and Grading and Dirt Haul Certificate.

SECTION 4: The City Council hereby declares that it would have passed this Ordinance sentence by sentence, paragraph by paragraph, and section by section, and does hereby declare that any provisions of this Ordinance are severable and if for any reason any sentence, paragraph or section of this Ordinance shall be held invalid, such decision shall not affect the validity of the remaining parts of this Ordinance.

SECTION 5: This Ordinance shall be published and posted according to law and shall take effect and be in force from and after 30 days after its passage and adoption. *****
I, City Clerk Crystal Mui, hereby certify that the foregoing Ordinance was introduced on the 9th day of October, 2023 and passed and adopted as an Ordinance of the City of San Carlos at a regular meeting thereof held on the 23rd day of October, 2023 by the following vote:
_______________________________
CITY CLERK of the City of San Carlos
APPROVED:

MAYOR of the City of San Carlos
Exhibits:

A. Zoning Map
B. Planned Development Plan
AYES, COUNCILMEMBERS:

NOES, COUNCILMEMBERS:

ABSENT, COUNCILMEMBERS:

7.e
October 23, 2023 Packet Pg. 28
4864-3640-1272 v2
C. Findings

7.e
October 23, 2023 Packet Pg. 29
4864-3640-1272 v2

EXHIBIT A

SAN CARLOS ZONING MAP
841 Old County Road (APN 046-133-160, 046-134-050, 046-134-060, 046-135-010, 046-135- 020, 046-135-030, 046-135-040, 046-182-100, 046-182-110, 046-182-150) zoned Planned Development (PD)

7.e
October 23, 2023 Packet Pg. 30
4864-3640-1272 v2

EXHIBIT B

PLANNED DEVELOPMENT PLAN

7.e
October 23, 2023 Packet Pg. 31

7.e
October 23, 2023 Packet Pg. 32

7.e
October 23, 2023 Packet Pg. 33

7.e
October 23, 2023 Packet Pg. 34

7.e
October 23, 2023 Packet Pg. 35

7.e
October 23, 2023 Packet Pg. 36

7.e
October 23, 2023 Packet Pg. 37

7.e
October 23, 2023 Packet Pg. 38

7.e
October 23, 2023 Packet Pg. 39

7.e
October 23, 2023 Packet Pg. 40

7.e
October 23, 2023 Packet Pg. 41

7.e
October 23, 2023 Packet Pg. 42

7.e
October 23, 2023 Packet Pg. 43

7.e
October 23, 2023 Packet Pg. 44

7.e
October 23, 2023 Packet Pg. 45

7.e
October 23, 2023 Packet Pg. 46

7.e
October 23, 2023 Packet Pg. 47

7.e
October 23, 2023 Packet Pg. 48

7.e
October 23, 2023 Packet Pg. 49

7.e
October 23, 2023 Packet Pg. 50

7.e
October 23, 2023 Packet Pg. 51

7.e
October 23, 2023 Packet Pg. 52

7.e
October 23, 2023 Packet Pg. 53

7.e
October 23, 2023 Packet Pg. 54

7.e
October 23, 2023 Packet Pg. 55

7.e
October 23, 2023 Packet Pg. 56

7.e
October 23, 2023 Packet Pg. 57

7.e
October 23, 2023 Packet Pg. 58

7.e
October 23, 2023 Packet Pg. 59

7.e
October 23, 2023 Packet Pg. 60

7.e
October 23, 2023 Packet Pg. 61

7.e
October 23, 2023 Packet Pg. 62

7.e
October 23, 2023 Packet Pg. 63

7.e
October 23, 2023 Packet Pg. 64

7.e
October 23, 2023 Packet Pg. 65

7.e
October 23, 2023 Packet Pg. 66

7.e
October 23, 2023 Packet Pg. 67

7.e
October 23, 2023 Packet Pg. 68

7.e
October 23, 2023 Packet Pg. 69

7.e
October 23, 2023 Packet Pg. 70

7.e
October 23, 2023 Packet Pg. 71

7.e
October 23, 2023 Packet Pg. 72

7.e
October 23, 2023 Packet Pg. 73

7.e
October 23, 2023 Packet Pg. 74

7.e
October 23, 2023 Packet Pg. 75

7.e
October 23, 2023 Packet Pg. 76

7.e
October 23, 2023 Packet Pg. 77

7.e
October 23, 2023 Packet Pg. 78

7.e
October 23, 2023 Packet Pg. 79

7.e
October 23, 2023 Packet Pg. 80

7.e
October 23, 2023 Packet Pg. 81

7.e
October 23, 2023 Packet Pg. 82

7.e
October 23, 2023 Packet Pg. 83

7.e
October 23, 2023 Packet Pg. 84

7.e
October 23, 2023 Packet Pg. 85

7.e
October 23, 2023 Packet Pg. 86

7.e
October 23, 2023 Packet Pg. 87

EXHIBIT C

REQUIRED FINDINGS FOR PLANNING COMMISSION CONSIDERATION 841 OLD COUNTY ROAD PROJECT
Planned Development Zoning and Planned Development Plan Findings:

In considering whether to recommend the Planned Development Zoning designation and Planned Development Plan, the City Council must consider the following findings.

A. The proposed development is consistent with the General Plan and any applicable specific plan, including the density and intensity limitations that apply.

Basis for Finding: The City does not have an adopted Specific Plans, however the East Side Innovation District Vision Plan is considered a guiding document for development in the area.

The project is consistent with the East Side Vision planning strategies within the area, including implementing the Discovery Path along Bransten Road, implementing the East Side connect multi-modal street, inclusion of an Activity Hub at the corner of Old County Road and Commercial Street, inclusion of a publicly accessible plaza space, promoting environmental stewardship and contribution towards community benefits. The project is consistent with the General Plan and the General Plan classification of Planned Industrial as outlined below. The project complies with the Heavy Industrial District development standards except for height, floor area and side yard setback.

General Plan Policies:
• LU-5.2: Implement the City’s adopted Economic Development Plan, which is updated annually as it relates to supporting the local economy. • LU-5.3: Support and encourage businesses and land uses that contribute to the City’s financial viability.
• LU-5.7: Support high-wage industries that provide quality jobs for workers at all education levels.
• LU-5.13: Consider use of multiple level parking facilities to provide increased space where available land is limited.
• LU-5.15: Promote economic revitalization on underutilized parcels designated for higher intensity land uses.
• LU-6.1: Support commercial/industrial activity and businesses on the East Side. • LU-6.2: Prohibit the conversion of property designated for industrial/commercial land on the East Side to non-industrial/commercial uses. ·Ensure proposed new uses in the East Side do not introduce land use conflicts that would adversely impact industrial/commercial activities.
• LU-6.3: Support the expansion of key growth industries while maintaining the overall diversity of land uses within East Side employment areas. • LU-6.6: Encourage new development on the East Side to feature high quality architecture that reinforces the character of the area. • LU-8.1: Require all development to feature high quality design that enhances the visual character of San Carlos.
• LU-8.3: Encourage design features and amenities in new development and redevelopment, including, but not limited to:
o Visual buffers.
o Facilitation of pedestrian activity.

7.e
October 23, 2023 Packet Pg. 88
o Distinctiveness and variety in architectural design
• LU-8.4: Promote pedestrian-scaled design through site planning, building design, finish details and landscaping for all types of development by requiring height and locational transitions between buildings of varied levels that are sensitive to the interrelationships of surrounding uses and structures, especially residential. • LU-8.5: Optimize architectural quality by encouraging the use of quality materials, particularly as accents and authentic detailing, such as balconies and window trims. • LU-8.8: Encourage design of convenient pedestrian walkways with shade and minimal tripping hazards, preferably with landscape buffers.
• LU-8.10: On all sides of buildings, require the incorporation of quality architectural design elements for all building façades and stepping back upper floors in order to reduce bulk and mass and to break up monotonous wall lines. • LU-8.18: Encourage “green building” practices in new development and redevelopment, such as those that make a building more energy efficient and reduces its effect on human health and the environment through better siting, design, construction, maintenance and operation.
• LU-11.1: Require high quality design for buildings at visually significant locations in gateway areas.
• LU-11.2: Encourage design features, such as landscaping, art and displays in gateway areas that are welcoming, attractive and contribute to a unique sense of place. • LU-11.3: Encourage distinctive architectural features, such as tower elements or a plaza at building entry, for buildings located at visually significant locations within gateway areas.
• CSH-3.1: Strive to reduce base-line and development-related traffic by 20 percent through public-private partnership efforts.
• CSH-3.2: Support city-wide efforts to reduce vehicular trips within and through the community.
• CSH-3.3 Support the incorporation of Transportation Demand Measures in new development to reduce traffic impacts.
• CSH-3.11: New developments and businesses shall be required to provide adequate loading, unloading and delivery areas, and/or shall be required to conduct such activities during nonbusiness/ peak hours
• EM-11.9 Coordinate with major employers, neighboring municipalities, transit agencies and providers to enhance regional transit and shuttle service.

B. The subject site is physically suitable for the type and intensity of the land use being proposed;
Basis for Finding: The proposed project is consistent with the General Plan land use classification, which seeks to allow retail service, office, research and development and industrial uses. This designation offers maximum flexibility for non-residential use. The research and development use would be compatible with other research and development uses in the surrounding area. The

3.41-acre site is large enough to accommodate the intensity of development while providing adequate landscaping, adequate on-site circulation and emergency access.

C. Adequate transportation facilities and public services exist or will be provided in accord with the conditions of PD plan approval, to serve the proposed development; and the approval of the proposed development will not result in a reduction of traffic levels of service or public services so as to be a detriment to public health, safety, or welfare;

7.e
October 23, 2023 Packet Pg. 89
Basis for Finding: The City has undertaken an environmental review of the project as required by the California Environmental Quality Act (CEQA), including a complete Initial Study/Mitigated Negative Declaration and a separate Transportation Impact Analysis. The analysis concluded that there will not be a significant reduction in traffic levels of service associated with the project. There are no anticipated public service concerns associated with the project that would be detrimental to the public health, safety, or welfare.

D. The proposed development will not have a substantial adverse effect on surrounding land uses and will be compatible with the existing and planned land use character of the surrounding area;
Basis for Finding: The project includes demolition of the existing buildings and construction of a new research and development office/lab. The project has been designed to be in scale with other proposed developments in the area including proposed developments at 789 Old County Road and 987 Commercial Street. The upper level of the building steps back from Old County Road to reduce the apparent mass of the building. Street trees are included along Old County Road, Commercial Street and Bransten Road to further screen the building.

E. The development generally complies with applicable adopted design guidelines; and Basis for Finding: The City does not have adopted design guidelines. The project has undergone review by City staff to ensure quality architecture. The building is designed with large windows at the ground level and upper level stepbacks to reduce apparent building mass. The building color and materials are high quality and appropriate for the area.

F. The proposed development is demonstratively superior to the development that could occur under the standards applicable to the underlying base district, and will achieve superior community design, environmental preservation and/or substantial public benefit. In making this determination, the following factors shall be considered:

1. Appropriateness of the use(s) at the proposed location.

2. The mix of uses, housing types, and housing price levels.

3. Provision of units affordable to persons and families of low and moderate income or to lower income households.

4. Provision of infrastructure improvements.

5. Provision of open space.

6. Compatibility of uses within the development area.

7. Creativity in design and use of land.

8. Quality of design, and adequacy of light and air to the interior spaces of the buildings.

9. Overall contribution to the enhancement of neighborhood character and the environment of San Carlos in the long term.

Basis for Finding: The proposed development complies with the development standards in the zoning code with the exception of height, floor area and exterior side yard setback. The property is located along Old County Road, Bransten Road and Commercial Street and is appropriate for higher intensity land use. The project includes contribution of community benefit that may be utilized to benefit the greater community.

Findings for Zoning Map Amendment:

7.e
October 23, 2023 Packet Pg. 90

1. The change in district boundaries is consistent with the purpose of this title to promote the growth of the City in an orderly manner and to promote and protect the public health, safety, peace, comfort and general welfare.

Basis for Finding: The change in district boundaries from Heavy Industrial to Planned Development maintains consistency with the underlying zoning land uses and development standards. The change in district boundaries is consistent with the zoning title and supports development of the site consistent with the economic development objectives of the City. The change in zoning will not impact public health, safety, peace, comfort and general welfare.

2. The change in district boundaries is necessary to achieve the balance of land uses desired by the City, consistent with the General Plan, and to increase the inventory of land within a given zoning district.

Basis for Finding: The change in zoning district boundaries from Heavy Industrial to Planned Development is necessary to support the economic development of the site consistent with the General Plan. The Planned Development Zoning regulations for the site maintains consistency with the Heavy Industrial zoning designation land uses and development standards. The change in district boundaries also maintains consistency with the General Plan designation of Planned Industrial which permits research and development (R&D), biotechnology, light industrial, flex space, warehousing and related uses. The project is consistent with General Plan policies to encourage new commercial development to expand the City’s tax base and to support the expansion of key growth industrials.

7.e
October 23, 2023 Packet Pg. 91

CITY COUNCIL

STAFF REPORT
MEETING DATE: October 23, 2023
ITEM TITLE: Adopt Ordinance 1602 Approving a Development Agreement with the Sobrato Family Foundation, for the 841 Old County Road Project.

RECOMMENDATION:

The Planning and Transportation Commission and staff recommend that the City Council adopt Ordinance 1602 approving a development agreement with the Sobrato Family Foundation for the 841 Old County Road Project (“Project”).

FISCAL IMPLICATIONS:

The Applicant has paid the appropriate application fees and provided deposit funds to pay for expenses related to the environmental review and other reports and analyses associated with the Project. The Project will be required to pay building permit fees and City impact fees. City impact fees total over $12.9 million and include commercial linkage (affordable housing), childcare, sewer, and traffic fees. The proposed development agreement includes community benefits, which are valued at $7.69 million.

The proposed development will also benefit the City with increased property tax, increased sales tax revenue, and new job creation. The estimated increased revenue to the City is $13.6 million over 20 years.

BACKGROUND:

The Planning and Transportation Commission, at its June 7, 2023 meeting, conducted a public hearing and adopted Resolution PTC2023-11 recommending that the City Council adopt the Mitigated Negative Declaration and associated Mitigation Monitoring and Reporting Program and adopted Resolution PTC2023-12 recommending that the City Council adopt the Ordinance to zone the site Planned Development (PD) Zoning, approve the associated Planned Development Plan, and adopt the Ordinance approving the development agreement. The Planning and Transportation Commission also approved the Design Review, Tentative Parcel Map, Transportation Demand Management Plan, and Grading and Dirt Haul Certificate subject to the approval of the Planned Development zoning.

The City Council heard the item at its August 28, 2023 meeting and continued the public hearing, requesting that the developer expand its community benefits offer. At its October 9, 2023 meeting, the City Council conducted the public hearing and adopted Resolution 2023-125 approving the Mitigated Negative Declaration and Mitigation Monitoring and Reporting Plan, introduced Ordinance 1601 to rezone the site from Heavy Industrial (IH) to Planned Development Zoning and approving the Planned Development Plan and introduced Ordinance 1602 approving the

7.f
October 23, 2023 Packet Pg. 92
development agreement as revised at the meeting.

ANALYSIS:

The development agreement includes construction of a new bike and pedestrian path along Bransten Road with landscape improvements, a community serving café with patio space, public access to a central landscaped courtyard, ability for community groups and non-profit organizations to reserve the central courtyard six times per year, four parking spaces for retail/cafe customer use, and 46 parking spaces available to the public on nights and weekends, including 2 EV charging stalls. At the October 9, 2023 City Council meeting, the developer also agreed to pre-plumb the development with purple pipe for future recycled water connection, provide an additional three parking spaces for guests visiting the courtyard, and include a booking system for community reservations. The community benefits also include monetary contributions to the City’s Downtown Improvement Fund, Community Improvement & Recreation Fund, and Green Energy Sustainability Fund, totaling $6,296,600 in monetary contributions to the City. The total community benefits are valued at $7,690,000 as outlined below. 841 Old County Road Community Benefits.

Downtown Improvement funds $2,796,600
Community Improvement & Recreation Fund $3,000,000
Green Energy Sustainability $500,000
Café (credit) $555,000
Bike/Pedestrian path (credit) $148,400
Public Parking (credit) $690,000
TOTAL $7,690,000
The development agreement is for a 10-year term and includes vesting of City laws and impact fee provisions.

The City Council, at its October 9, 2023 meeting, introduced Ordinance 1602 approving the development agreement with the following amendments to:
- add three additional public parking spaces during business hours, for a total of seven spaces, to be available for public visiting the cafe and/or courtyard space; - pre-plumb the development with purple pipe for future recycled water connection; and - include a booking system for community reservations of the courtyard space.

Environmental Review.

The City Council adopted Resolution 2023-125 approving the Mitigated Negative Declaration and Mitigation Monitoring Plan prepared in accordance with CEQA guidelines. With implementation of the mitigation measures, the project will not result in a significant impact to the environment.

7.f
October 23, 2023 Packet Pg. 93
ALTERNATIVES:

The alternatives available to the City Council include:

1. Adopt Ordinance 1602 approving a Development Agreement with the Sobrato Family Foundation for the 841 Old County Road Project; or

2. Do not adopt the Ordinance; or

3. Provide staff with alternative direction.

Respectfully submitted by:

Al Savay, Community Development Director
Approved for submission by:
_______________________
Jeff Maltbie, City Manager
ATTACHMENT(S):

1. Ordinance 1602 with Exhibit A – Findings
Exhibit B to Ordinance – Development Agreement

2. Development Agreement Redlined Pages to Show Updates Since Ordinance 1st Reading

7.f
October 23, 2023 Packet Pg. 94
4856-2172-3000 v2
ORDINANCE NO. 1602

AN ORDINANCE OF THE CITY OF SAN CARLOS

APPROVING A DEVELOPMENT AGREEMENT WITH THE SOBRATO FAMILY FOUNDATION, FOR THE 841 OLD COUNTY ROAD PROJECT.

WHEREAS, The Sobrato Family Foundation, a California nonprofit public benefit corporation, is the fee owner of the property located at 800-851 Old County Road, San Carlos, California and identified as Assessor Parcel Numbers 046-133-160, 046-134-050, 046-134-060, 046-135-010, 046-135-020, 046-135-030, 046-138-040, 046-182-100, 046-182-110, and 046- 182-150 (the “Property”); and
WHEREAS, pursuant to Title 18 of the City of San Carlos Municipal Code (“SCMC”) and California Government Code Sections 65864 to 65869.5, SI 74, LLC, a California limited liability company, filed an application for approval of a development agreement for the Property in conjunction with its application for a Planned Development Plan and accompanying Zoning Map Amendment, Design Review, Grading and Dirt Haul Certificate, Tentative Parcel Map and Transportation Demand Management Plan to facilitate the development of a research and development campus that will include two office/laboratory buildings, which total approximately 339,170 square feet with below grade parking (the “Project”); and WHEREAS, SI 74, LLC, submitted an application for a development agreement and later transferred title to Sobrato Family Foundation, a California nonprofit public benefit corporation.

Both entities are controlled by members of the Sobrato family. Following the transfer, the City updated the application to reflect that the Sobrato Family Foundation, a California nonprofit public benefit corporation, is the owner of the Property and the applicant; and WHEREAS, by Resolution PTC2023-11, adopted on June 7, 2023, the Planning and Transportation Commission recommended that the City Council adopt the Mitigated Negative Declaration for the Project (MND) and adopt the Mitigation Monitoring and Reporting Plan for the Project (MMRP) pursuant to the California Environmental Quality Act (CEQA) for the implementation of the mitigation measures outlined in the MND; and WHEREAS, by Resolution PTC2023-12, adopted on June 7, 2023, the Planning and Transportation Commission recommended that the City Council adopt an Ordinance approving the Zoning Map Amendment to change the site from Heavy Industrial (IH) Zoning District to Planned Development (PD) Zoning District and adopt the Planned Development Plan; and WHEREAS, the Planning and Transportation Commission discussed the specific terms of the development agreement and recommended that the City Council approve the development agreement by Resolution PTC-2023-12, adopted on June 7, 2023; and WHEREAS, at a duly noticed public hearing held on June 7, 2023, the Planning and Transportation Commission approved the Design Review, Grading and Dirt Haul Certificate, the Tentative Parcel Map, and the Transportation Demand Management Plan, subject to approval of the Planned Development Plan and effective on the effective date of the Planned Development Plan; and

7.f
October 23, 2023 Packet Pg. 95
4856-2172-3000 v2
WHEREAS, by Resolution 2023-125, adopted October 9, 2023, the City Council made findings and adopted the MND and the MMRP pursuant to CEQA for the implementation of the mitigation measures outlined in the MND; and
WHEREAS, the City Council of the City of San Carlos held a duly noticed public hearing on August 28, 2023 and introduced an ordinance amending the Zoning Map to change the site from Heavy Industrial Zoning District (IH) to Planned Development Zoning District (PD) and adopted the Planned Development Plan; and
WHEREAS, the City Council of the City of San Carlos held a duly noticed public hearing regarding the adoption of the Development Agreement on October 9, 2023.

NOW THEREFORE THE CITY OF SAN CARLOS DOES HEREBY ORDAIN AS FOLLOWS:

SECTION 1: The City Council finds that the Project is a development for which a development agreement is appropriate in order to: 1) eliminate uncertainty in the City’s land use planning for the project and provide for the orderly development of the project; 2) assure installation of necessary improvements on the property; 3) provide for the public infrastructure and services appropriate to the development of the project; 4) secure City improvements that benefit the community; 5) provide for the developer to deliver community benefits in excess of those that the City could require as conditions of approval; and 6) otherwise achieve the goals and purposes of Chapter 18.37 of the SCMC.

SECTION 2: The City Council finds that the development agreement is consistent with the General Plan as described in Exhibit A.

SECTION 3: The City Council hereby approves the development agreement included as Exhibit B and the City Manager is hereby authorized to execute the development agreement on behalf of the City. The City Manager is further authorized, with concurrence of the City Attorney, to approve minor, non-monetary amendments to the development agreement that are necessary for the development of the Project as contemplated in the development agreement.

SECTION 4: Severability. The City Council hereby declares that it would have passed this Ordinance sentence by sentence, paragraph by paragraph, and section by section, and does hereby declare that any provisions of this Ordinance are severable and if for any reason any sentence, paragraph or section of this Ordinance shall be held invalid, such decision shall not affect the validity of the remaining parts of this Ordinance.

SECTION 5: Publication and Effective Date. This Ordinance shall be published and posted according to law and shall take effect and be in force from and after 30 days after its passage and adoption.
****
I, City Clerk Crystal Mui, hereby certify that the foregoing Ordinance was introduced on the 9th day of October, 2023 and passed and adopted as an Ordinance of the City of San Carlos at a regular meeting thereof held on the 23rd day of October, 2023 by the following vote:

7.f
October 23, 2023 Packet Pg. 96
4856-2172-3000 v2
AYES, COUNCILMEMBERS: __________________________________________________ NOES, COUNCILMEMBERS: _________________________________________________ ABSENT, COUNCILMEMBERS: _______________________________________________ ______________________________
CITY CLERK of the City of San Carlos
APPROVED:

MAYOR of the City of San Carlos
Exhibits:

A. Consistency with the General Plan - Findings
B. Development Agreement

7.f
October 23, 2023 Packet Pg. 97
4856-2172-3000 v2
Exhibit A
Development Agreement Finding:

In considering whether to approve the Development Agreement, the City Council must find the Development Agreement consistent with the General Plan.

Basis for Finding: The Development Agreement and provision of community benefits including the new pedestrian/bicycle pathway, publicly accessible open space, community serving cafe and financial contributions are consistent with the following General Plan policies:
• LU-1.12: Promote the development of publicly accessible urban trails throughout the city to provide access to the natural environment and facilitate nonmotorized transportation options.
• LU-3.10: Encourage the creation of safe, walkable environments that include elements such as wide, smooth sidewalks, good lighting, safe crosswalks, clear signage, curb bulb-outs, curb cuts, street furniture and trees and traffic-calming measures which allow people of all ages and abilities to exercise and safely access public transportation, community centers and schools and goods and services.
• LU-8.9: Encourage the design of attractive outdoor pedestrian spaces that encourage impromptu public gathering places with features such as plazas, interior walkways and paseos, ornamental gates, trellises, lighting, trees and landscaping, seating and fountains.
• CHS-7.1: Trails and paths intended for general circulation shall provide reasonably direct and convenient routes of travel for potential users.
• CHS-7.7: Public trails should be located and designed so that they serve the needs of the public while minimizing private property impacts.

7.f
October 23, 2023 Packet Pg. 98
4856-2172-3000 v2
Exhibit B
Development Agreement

7.f
October 23, 2023 Packet Pg. 99
4856-1780-3355 v21

RECORDING REQUESTED BY

AND WHEN RECORDED
RETURN TO:

City of San Carlos
600 Elm Street
San Carlos, California 94070
Attn: City Clerk
Space Above This Line Reserved for Recorder’s Use
Exempt from Recording Fee Per Government Code
Section 27383

DEVELOPMENT

AGREEMENT
by and between the

CITY OF SAN CARLOS,
a California municipal
corporation and

THE SOBRATO FAMILY FOUNDATION,
a California nonprofit public benefit corporation
regarding the
841 Old County Road Project
Effective Date: _____________

7.f
October 23, 2023 Packet Pg. 100
i

TABLE OF CONTENTS
Page
ARTICLE 1 DEFINITIONS............................................................................................................3

1.1 Definitions .......................................................................................................................3 ARTICLE 2 EFFECTIVE DATE AND TERM ..............................................................................7

2.1 Effective Date ..................................................................................................................7

2.2 Term.................................................................................................................................7

2.3 City Representations and Warranties...............................................................................8

2.4 Developer Representations and Warranties.....................................................................8 ARTICLE 3 DEVELOPMENT OF PROPERTY............................................................................9

3.1 Vested Rights...................................................................................................................9

3.2 Reservations of Authority................................................................................................9

3.3 Regulation by Other Public Agencies............................................................................10

3.4 Life of Project Approvals; Termination.........................................................................11

3.5 Initiatives .......................................................................................................................12

3.6 No Affirmative Obligation to Develop; Timing of Development .................................12

3.7 No Conflicting Enactments............................................................................................13

3.8 Changes in the Law........................................................................................................13

3.9 No Reservation of Sanitary Sewer or Potable Water Capacity .....................................13 ARTICLE 4 FEES AND OTHER CHARGES..............................................................................14

4.1 City Fees. .......................................................................................................................14

4.2 Other Agency Fees.........................................................................................................14

4.3 Taxes and Assessments..................................................................................................15 ARTICLE 5 DEVELOPER COMMUNITY BENEFITS COMMITMENTS ..............................15

5.1 Public Benefits...............................................................................................................15

5.2 Community Benefits......................................................................................................16 ARTICLE 6 ANNUAL REVIEW .................................................................................................19

6.1 Periodic Review.............................................................................................................19

6.2 Certificate of Good Faith Compliance...........................................................................20

6.3 No Waiver......................................................................................................................20

6.4 Reimbursement of Annual Review Costs......................................................................20 ARTICLE 7 MORTGAGEE PROTECTION................................................................................21

7.1 Mortgagee Protection.....................................................................................................21

7.2 Mortgagee Not Obligated ..............................................................................................21

7.3 Notice of Default to Mortgagee; Right to Cure .............................................................21

7.4 No Supersedure..............................................................................................................22

7.5 Technical Amendments to this Article 7 .......................................................................22 ARTICLE 8 AMENDMENT OF AGREEMENT AND PROJECT APPROVALS.....................22

7.f
October 23, 2023 Packet Pg. 101
ii

8.1 Amendment of this Agreement......................................................................................22

8.2 Amendments to Development Agreement Statute.........................................................24

8.3 Amendments to Project Approvals................................................................................24

8.4 Reliance on Initial Study and MND ..............................................................................25

8.5 Subsequent CEQA Review............................................................................................25 ARTICLE 9 COOPERATION AND IMPLEMENTATION........................................................25

9.1 Additional Project Approvals ......................................................................................25

9.2 Scope of Review of Additional Project Approvals........................................................26

9.3 Processing Applications for Additional Project Approvals...........................................26

9.4 Other Agency Additional Project Approvals; Authority of City...................................26

9.5 Implementation of Necessary Mitigation Measures and Conditions.............................27

9.6 Cooperation in the Event of Legal Challenge................................................................27

9.7 Revision to Project.........................................................................................................29

9.8 State, Federal or Case Law ............................................................................................29

9.9 Compliance with Laws ..................................................................................................29

9.10 Indemnity and Hold Harmless.......................................................................................30

9.11 Sales Tax Point of Sale Designation..............................................................................31 ARTICLE 10 ASSIGNMENT.......................................................................................................31

10.1 Transfers ........................................................................................................................31 ARTICLE 11 DEFAULT; REMEDIES; TERMINATION ..........................................................33

11.1 Breach and Default ........................................................................................................33

11.2 Withholding of Permits..................................................................................................33

11.3 Termination....................................................................................................................33

11.4 Specific Performance for Violation of a Condition .......................................................33

11.5 Resolution of Disputes...................................................................................................33

11.6 Rights and Remedies Are Cumulative...........................................................................34

11.7 Limitation on Damages..................................................................................................34

11.8 Surviving Provisions......................................................................................................35 ARTICLE 12 MISCELLANEOUS PROVISIONS.......................................................................35

12.1 Incorporation of Recitals, Exhibits and Introductory Paragraph ...................................35

12.2 Severability ....................................................................................................................35

12.3 Construction...................................................................................................................35

12.4 Covenants Running with the Land.................................................................................36

12.5 Notices...........................................................................................................................36

12.6 Counterparts and Exhibits; Entire Agreement ...............................................................37

12.7 Recordation of Agreement.............................................................................................37

12.8 No Joint Venture or Partnership ....................................................................................37

12.9 Waivers..........................................................................................................................37

12.10 California Law; Venue...................................................................................................38

12.11 City Approvals and Actions...........................................................................................38

12.12 Estoppel Certificates......................................................................................................38

12.13 No Third Party Beneficiaries.........................................................................................38

12.14 Signatures.......................................................................................................................38

7.f
October 23, 2023 Packet Pg. 102
iii

12.15 Time ...............................................................................................................................38

12.16 Days...............................................................................................................................38

LIST OF EXHIBITS
Exhibit A Property Legal Description
Exhibit B Impact Fees
Exhibit C Initial Shell Condition
Exhibit D [Form of] POPA Easement
Exhibit E [Form of] Public Parking Agreement
Exhibit F [Form of] Assignment & Assumption Agreement
Exhibit G Parking Exhibit

7.f
October 23, 2023 Packet Pg. 103
1 DEVELOPMENT

AGREEMENT
THIS DEVELOPMENT AGREEMENT (“Agreement”) dated for reference purposes as of the Effective Date, is entered into by and between the CITY OF SAN CARLOS, a California municipal corporation organized and existing under the laws of the State of California (“City”) and THE SOBRATO FAMILY FOUNDATION, a California nonprofit public benefit corporation (“Developer”). City and Developer are sometimes referred to individually herein as a “Party” and collectively as “Parties.”

R E C I T A L S
The following recitals are a substantive part of this Agreement; capitalized terms used herein and not otherwise defined are defined in Section 1.1 of this Agreement.

A. In order to strengthen the public planning process, encourage private participation in comprehensive planning and reduce the economic costs and risk of development, the Legislature of the State of California enacted Section 65864 et seq. of the Government Code (“Development Agreement Statute”) which authorizes a city and a developer having a legal or equitable interest in real property to enter into a binding, long-term development agreement, establishing certain development rights in the property. This Agreement has been drafted and processed pursuant to the Development Agreement Statute.

B. Developer owns fee title to the approximately 3.4 acres of real property located at 803-851 Old County Road, San Carlos, California (APNs 046-133-160, 046-134-050, 046-134- 060, 046-135-010, 046-135-020, 046-135-030, 046-138-040, 046-182-100, 046-182-110 and 046- 182-150), more fully described on Exhibit A, attached and incorporated herein by reference (the “Property”). The Property is located in the heart of the East Side Innovation District in San Marcos and is currently occupied by a garden supply center, kennels and a tree services office.

C. Developer wishes to redevelop the Property, consistent with the East Side Innovation District Vision Plan, as a mixed-use office and R&D/life sciences development with approximately 339,170 gross square feet (“gsf”) of office, R&D and life sciences uses; including a southern structure along Commercial Street that is approximately 90’-6’’ at the top of the roof parapet and approximately 99’ at the top of the mechanical screen, and a northern structure along Bransten that is approximately 74’6’’ at the top of the roof parapet and approximately 83’ at the top of the mechanical screen. The buildings may be built in phases, include two levels of below grade parking and have a central plaza and courtyard between them (collectively, the “841 Old County Road Project” or the “Project”).

D. To achieve the Parties’ mutual goals of redevelopment as expeditiously as possible, the Developer desires to receive assurance that it may proceed with the Project in accordance with the Applicable City Regulations. Therefore, this Agreement between City and Developer sets forth, among other things, the applicable fees, policies and zoning requirements that will apply to Developer’s development of the Project and provides Developer with a vested right to develop the Project.

7.f
October 23, 2023 Packet Pg. 104
2 E. Approval and development of the Project relies on the following analysis under the California Environmental Quality Act (“CEQA”) (set forth in Public Resources Code, Section 21000 et seq.) and the State CEQA Guidelines (“CEQA Guidelines”) (set forth in California Code of Regulations section 15000 et seq.): (1) an Initial Study/Mitigated Negative Declaration prepared by Lamphier-Gregory (“IS/MND”), to be adopted by the City Council; and (2) a Mitigation Monitoring and Reporting Program (“MMRP”), concluding that no additional environmental review is necessary.

F. Prior to approval of this Agreement, the City has taken the following actions in connection with the development of the Project on the Property:
(a) Adoption of the IS/MND by the City Council by Resolution No. ____ on _____;
(b) Approval of the MMRP by Resolution No. ____, adopted by the City Council on _____;
(c) Approval of the Tentative Map by the Planning and Transportation Commission on June 7, 2023;
(d) Approval of the Zoning Map Amendment and Planned Development Plan by Ordinance No. __ adopted by the City Council on ____ to allow site specific standards as follows:
(i) Building height;
(ii) Floor area ratio;
(iii) Above grade setback along Commercial Street;
(iv) Below grade setback from property line for parking structure; and (v) Parking lot tree planting requirement for the grade level roof of the structured, below grade parking;
(e) Approval of Design Review Certificate by the Planning and Transportation Commission on June 7, 2023;
(f) Approval of the Transportation Demand Management Plan by the Planning Commission on June 7, 2023; and
(g) Approval of Grading and Dirt Haul Certificate by the Planning and Transportation Commission on June 7, 2023.

The approvals and development policies described in this Recital F, together with the MMRP and this Agreement, are collectively referred to herein as the “Project Approvals.”

7.f
October 23, 2023 Packet Pg. 105
3 G. The Development Agreement Statute provides that the purpose of development agreements is to strengthen the public planning process, encourage comprehensive planning, obtain private participation in meeting community needs, and reduce uncertainty in the approval of development. The City has determined that by entering into this Agreement, City will further the purposes set forth in the Development Agreement Statute and City will benefit from the redevelopment of the Property, public parking, financial contributions and other benefits provided in this Agreement.

H. The terms and conditions of this Agreement have undergone review by City staff, the Planning and Transportation Commission and the City Council at publicly noticed meetings and have been found to be fair, just and reasonable and in conformance with the goals, policies, standards and land use designations specified in the City’s General Plan and the East Side Innovation District Vision Plan and, further, the City Council finds that the economic interests of City’s citizens and the public health, safety and welfare will be best served by entering into this Agreement.

I. On June 7, 2023, after a duly noticed public hearing, the Planning Commission, the initial hearing body for purposes of development agreement review, adopted its Resolution No.

PC2023-12 recommending approval of this Agreement to the City Council. After duly noticed public hearings, on [________], the City Council introduced Ordinance No. [_____] approving this Agreement (“Enacting Ordinance”), and adopted it on [________]. The Enacting Ordinance will become effective on [__________], thirty (30) days thereafter.

A G R E E M E N T
NOW, THEREFORE, in consideration of the promises, covenants and provisions set forth herein, the receipt and adequacy of which is hereby acknowledged, the Parties agree as follows:

ARTICLE 1

DEFINITIONS

1.1 Definitions.
“Additional Project Approvals” is defined in Section 9.1. “Administrative Project Amendment” is defined in Section 8.3.2. “Affiliate of Developer” means an entity or person that directly or indirectly controls, is controlled by, or is under common control with Developer. For the purposes of this definition, “control” means the possession, direct or indirect, of the power to direct or cause the direction of the management and policies of an entity or person, whether through the ownership of voting securities, by contract, or otherwise, and the terms “controlling” and “controlled” have the meanings correlative to the foregoing.
“Agreement” means this Development Agreement.
“Agreement Amendment” is defined in Section 8.1.3.

7.f
October 23, 2023 Packet Pg. 106
4 “Applicable City Regulations” means (a) all City policies, standards and specifications set forth in this Agreement and the Project Approvals, including the specific conditions of approval adopted with respect to the Project Approvals; (b) with respect to matters not addressed by this Agreement or the Project Approvals but governing permitted uses of the Property, building locations, sizes, densities, intensities, design and heights, site design, setbacks, lot coverage and open space, and parking, those City ordinances, rules, regulations, official policies, standards and specifications in force and effect on the Effective Date; and (c) with respect to all other matters, including building, plumbing, mechanical and electrical codes, those New City Laws which may be applied to the Project and Developer pursuant to the terms of this Agreement, including but not limited to Section 3.2.
“Applicable Laws” means (a) all State and Federal laws and regulations applicable to the Property and the Project as enacted, adopted and amended from time to time; and (b) the Applicable City Regulations.
“Biosafety Levels” means those levels used to identify the protective measures needed in biomedical laboratory setting to protect workers, the environment, and the public and as defined in the Biosafety in Microbiology and Biomedical Laboratories (BMBL) 6th Edition published by the Centers for Disease Control and Prevention and National Institutes of Health. “Certificate of Occupancy” or “COO” means an official document issued by the City Building Official that certifies that the building (not including any tenant improvements) proposed as part of the Project has been inspected and determined to comply with the Project Approvals, including the applicable California Building Standards Code and the City’s local ordinances which govern construction and occupancy. A “temporary” COO confirms the building is safe for the proposed temporary use or occupancy but is still subject to a punch list of items required to be complete to obtain a final COO. A “final” COO means the building has been inspected and determined safe for the proposed use and occupancy and all final punch list items are complete. “CEQA” is defined in Recital E.
“CEQA Guidelines” is defined in Recital E.
“Changes in the Law” is defined in Section 3.8.
“City” means the City of San Carlos, a California municipal corporation. “City Party” and “City Parties” are defined in Section 9.10. “Claims” means liabilities, obligations, orders, claims, damages, fines, penalties and expenses, including reasonable attorneys’ fees (which may include, without limitation, reasonable City Attorney’s time as a pass-through cost without markup) and costs. “Connection Fees” means those fees charged by City or by a utility provider to utility users as a cost for connecting to water, sanitary sewer and other applicable utilities. “Community Benefits” is defined in Section 6.1.

7.f
October 23, 2023 Packet Pg. 107
5 “Community Benefit Space” is defined in Section 5.2.4. “Community Benefit Use” is defined as a Restaurant and Coffee Shop Use (defined below), Retail Sales (excluding Cannabis Dispensaries and Retail Establishments Selling Ammunition or Firearms), Instructional Services, Animal Care, Sales and Services (excluding Veterinary Services), Personal Services (excluding Tattoo or Body Modification Parlor), Government Offices, and Cultural Institutions, all as defined in Chapter 18.40 of the San Carlos Municipal Code.
“Community Development Director” means the Director of Community Development of the City of San Carlos, or his/her designee.
“Default” is defined in Section 11.1.
“Developer” means The Sobrato Family Foundation, a California nonprofit public benefit corporation, and its permitted assignees and successors-in-interest under this Agreement. “Development Agreement Statute” is defined in Recital A. “Effective Date” is defined in Section 2.1.
“Enacting Ordinance” is defined in Recital I.
“Exactions” means exactions that may be imposed by the City as a condition of developing the Project, including requirements for acquisition, dedication or reservation of land; and obligations to construct on-site or off-site public and private infrastructure improvements such as roadways, utilities or other improvements necessary to support the Project, whether such exactions constitute subdivision improvements, mitigation measures in connection with environmental review of the Project, or impositions made under Applicable City Regulations. For purposes of this Agreement, Exactions do not include Impact Fees.
“Expiration Date” is defined in Section 2.2.1.
“Force Majeure Delay” is defined in Section 2.2.2.
“Impact Fees” means the monetary amount charged by City in connection with a development project for the purpose of defraying all or a portion of the cost of mitigating the impacts of the development project or development of the public facilities related to the development project, including, any “fee” as that term is defined by Government Code Section 66000(b). For purposes of this Agreement, a fee that meets both the definitions of an Impact Fee and an Exaction, will be considered to be an Impact Fee. Impact Fees do not include Other Agency Fees.
“Initial Shell Condition” is defined in Exhibit C.
“IS/MND” is defined in Recital E.
“Litigation Challenge” is defined in Section 9.6.

7.f
October 23, 2023 Packet Pg. 108
6 “MMRP” is defined in Recital E.
“Mortgage” is defined in Section 7.1.
“Mortgagee” is defined in Section 7.1.
“New City Laws” means and includes any ordinances, resolutions, orders, rules, official policies, standards, specifications, guidelines or other regulations, which are promulgated, adopted, enacted or amended by the City (including but not limited to any City agency, body, department, officer or employee) or its electorate (through the power of initiative or otherwise) after the Effective Date.
“Operating Memorandum” is defined in Section 8.1.2.
“Other Agency Fees” is defined in Section 4.2.
“Other Agency Additional Approvals” means Additional Project Approvals to be obtained from entities other than City.
“Party/Parties” is defined in the introductory paragraph preceding the Recitals of this Agreement.
“Planning Commission” means the Planning Commission of the City of San Carlos. “POPA Easement” is defined in Section 5.1.
“Prevailing Wage Laws” is defined in Section 9.9.
“Processing Fees” means all fees for processing development project applications, including any required supplemental or other further environmental review, plan checking and inspection and monitoring for land use approvals, design review, grading and building permits, General Plan maintenance fees, encroachment permits, and other permits and entitlements required to implement the Project, which are in effect at the time those permits, approvals or entitlements are applied for and in effect at the time such work occurs, and which are intended to cover the actual costs of processing the foregoing, and which may include the cost of retaining outside contractors for plan checking or other purposes and City’s administrative expenses related to such retention as set forth in Section 9.3.
“Project” is defined in Recital C.
“Project Approvals” is defined in Recital F.
“Property” is defined in Recital B.
“Restaurant/Coffee Shop Use” is defined as any Eating and Drinking Establishment (excluding night clubs).
“Term” is defined in Section 2.2.1.

7.f
October 23, 2023 Packet Pg. 109
7 ARTICLE 2

EFFECTIVE DATE AND TERM

2.1 Effective Date. This Agreement shall become effective upon the later to occur of (i) the date the Enacting Ordinance is effective and (ii) execution by the Parties (“Effective Date”).

2.2 Term.

2.2.1 Term of Agreement. The “Term” of this Agreement shall commence on the Effective Date and shall expire upon the earliest to occur of the following: (1) the issuance of a final Certificate of Occupancy for the Project; (2) termination of this Agreement in accordance with its terms, including without limitation this Section

2.2; or (3) the tenth (10th) anniversary of the Effective Date. Upon such termination, this Agreement shall be deemed terminated and of no further force and effect, subject, however, to the extension provisions set forth in Section 2.2.2 and Section

2.2.3, and subject to Section 11.8 below and those provisions that expressly survive termination. Termination of the Term as it may be extended is referred to herein as the “Expiration Date.” City shall have the right to extend the Term if it deems necessary for Developer to satisfy all its obligations under this Agreement.

2.2.2 Enforced Delay; Extension of Times of Performance. Subject to the limitations set forth below, performance by either Party hereunder shall not be deemed to be in Default, and all performance and other dates specified in this Agreement shall be extended (except as otherwise excluded or qualified herein), where delays are due to: war; insurrection; strikes and labor disputes; lockouts; riots; floods; earthquakes; fires; casualties; acts of God; acts of the public enemy; pandemics or epidemics; quarantine restrictions; freight embargoes; governmental restrictions or priority; litigation and arbitration, including court delays; legal challenges to this Agreement, the Project Approvals, or any other approval required for the Project or any initiatives or referenda regarding the same; environmental conditions, preexisting or discovered; unusually severe weather but only to the extent that such weather or its effects (including, without limitation, dry out time) result in delays that cumulatively exceed twenty (20) days for every winter season occurring after Commencement of Construction of the Project; acts or omissions of the other party; or acts or failures to act of any public or governmental agency or entity (except that acts or failures to act of City shall not excuse performance by City); moratorium (each a “Force Majeure Delay”). An extension of time for any such cause shall be for the period of the enforced delay and shall commence to run from the time of the commencement of the cause, if written notice by the party claiming such extension is sent to the other party within sixty (60) days of the commencement of the cause.

If written notice is sent after such sixty (60) day period, then the extension shall commence to run no sooner than sixty (60) days prior to the giving of such notice.

Times of performance under this Agreement may also be extended in writing by the mutual agreement of City and Developer. The Term of this Agreement shall not be subject to extension for any Force Majeure Delay.

7.f
October 23, 2023 Packet Pg. 110
8 2.2.3 Extension of Term for Commencement of Construction of the Project. If the Developer is in good faith compliance with this Agreement and has commenced construction of the South Building (as defined below), the City Manager may in his or her reasonable discretion enter in an Insubstantial Amendment to extend the Term until a final Certificate of Occupancy has been issued for all buildings and structures shown in the Project Approvals; provided, however, that the extension shall not exceed two (2) years and notwithstanding such extension, subject to Force Majeure and all applicable notice and opportunity to cure, the Term shall expire and this Agreement shall terminate if after commencement of construction of the Project, work stops for more than six (6) consecutive months. Upon such termination, this Agreement shall be deemed terminated and of no further force and effect except for those provisions that expressly survive termination.

2.3 City Representations and Warranties. City represents and warrants to Developer that, as of the Effective Date:

2.3.1 City is a municipal corporation, and has all necessary powers under the laws of the State of California to enter into and perform the undertakings and obligations of City under this Agreement.

2.3.2 The execution and delivery of this Agreement and the performance of the obligations of City hereunder have been duly authorized by all necessary City Council action and all necessary approvals have been obtained.

2.3.3 This Agreement is a valid obligation of City and is enforceable in accordance with its terms.

During the Term of this Agreement, City shall, upon learning of any fact or condition which would cause any of the warranties and representations in this Section 2.3 not to be true, immediately give written notice of such fact or condition to Developer.

2.4 Developer Representations and Warranties. Developer represents and warrants to City that, as of the Effective Date:

2.4.1 Developer is duly organized and validly existing under the laws of the State of California, and is in good standing and has all necessary powers under the laws of the State of California to own property interests and in all other respects enter into and perform the undertakings and obligations of Developer under this Agreement.

2.4.2 The execution and delivery of this Agreement and the performance of the obligations of Developer hereunder have been duly authorized by all necessary company action and all necessary member approvals have been obtained.

2.4.3 This Agreement is a valid obligation of Developer and is enforceable in accordance with its terms.

7.f
October 23, 2023 Packet Pg. 111
9 2.4.4 Developer has not (i) made a general assignment for the benefit of creditors, (ii) filed any voluntary petition in bankruptcy or suffered the filing of any involuntary petition by Developer’s creditors, (iii) suffered the appointment of a receiver to take possession of all, or substantially all, of Developer’s assets, (iv) suffered the attachment or other judicial seizure of all, or substantially all, of Developer’s assets, (v) admitted in writing its inability to pay its debts as they come due, or (vi) made an offer of settlement, extension or composition to its creditors generally.

During the Term of this Agreement, Developer shall, upon learning of any fact or condition which would cause any of the warranties and representations in this Section 3.4 not to be true, immediately give written notice of such fact or condition to City.

ARTICLE 3

DEVELOPMENT OF PROPERTY

3.1 Vested Rights. The City hereby grants to Developer the present vested right to develop and construct on the Property all the improvements authorized by, and in accordance with, the Project Approvals. To the extent permitted by Applicable Laws, and except as otherwise provided herein, no future modification of the City’s General Plan, Municipal Code, ordinances, policies or regulations shall apply to the Property that purports to: (i) limit the permitted uses of the Property, the density and intensity of use, or the maximum height and size of proposed buildings; (ii) impose requirements for reservation or dedication of land for public purposes or requirements for infrastructure, public improvements, or public utilities, other than as provided in the Project Approvals or pursuant to this Agreement; (iii) impose conditions upon development of the Property other than as permitted by the Applicable Laws, Changes in the Law, the Project Approvals and this Agreement; (iv) limit the timing, phasing or rate of development of the Property; provided, however, that nothing in this Agreement shall prevent or preclude City from adopting any land use ordinances, policies, regulations or amendments permitted herein or relieve Developer of its obligation to develop the Property within the times provided in this Agreement; (v) limit the location of building sites, grading or other improvements on the Property in a manner that is inconsistent with or substantially more restrictive than the limitations included in this Agreement or the Project Approvals; (vi) frustrate in a more than insignificant way the intent or purpose of the Project Approvals in relation to the Project; (vii) limit or control the ability to obtain public utilities, services, or facilities; (viii) require the issuance of additional permits or approvals by the City other than those required by Applicable Laws; or (ix) limit the processing or procuring of applications and approvals of Additional Project Approvals.

3.2 Reservations of Authority. The Parties acknowledge and agree that City is restricted in its authority to limit its police power by contract. This Agreement shall be construed to reserve to City all such power and authority which cannot be restricted by contract.

Notwithstanding any other provision of this Agreement to the contrary, the following regulations and provisions shall apply to the development of the Project:

7.f
October 23, 2023 Packet Pg. 112
10 3.2.1 Except as otherwise provided in Section 4.1 Processing Fees, Connection Fees and other fees of every kind and nature imposed by the City, and any increase or modification to those fees that are in force and effect at the time land use or development permits, approvals or entitlements are applied for or issued on any or all portions of the Project.

3.2.2 Regulations relating to hearing bodies, petitions, applications, notices, findings, records, hearings, reports, recommendations, appeals and any other matter of procedure then applicable in City at the time of permit application.

3.2.3 Regulations governing construction standards and specifications, including City’s building code, plumbing code, mechanical code, electrical code, fire code and grading code, and all other uniform construction codes then applicable in City at the time of permit application.

3.2.4 New City Laws applicable to the Property or Project, which do not conflict with this Agreement.

3.2.5 New City Laws which may be in conflict with this Agreement but which are necessary to protect persons or property from dangerous or hazardous conditions which create a threat to the public health or safety or create a physical risk, based on findings by the City Council identifying the dangerous or hazardous conditions requiring such changes in the law, why there are no feasible alternatives to the imposition of such changes, and how such changes would alleviate the dangerous or hazardous condition. City’s decision to apply New City Laws to the Project shall be reviewed based on substantial evidence, and this section shall not be construed to impose the requirements set forth in Government Code Section 65589.5.

3.2.6 The Property shall be subject to any New City Laws regulating or prohibiting laboratory uses classified as Biosafety Level 3 or 4, regardless of whether those New City Laws conflict with this Agreement, the Applicable City Regulations, or the Project Approvals.

3.2.7 Exactions required by this Agreement, the Project Approvals or any Additional Project Approvals.

3.3 Regulation by Other Public Agencies. Developer acknowledges and agrees that other public agencies not within the control of City possess authority to regulate aspects of the development of the Property separately from or jointly with City, and this Agreement does not limit the authority of such other public agencies. Developer shall, at the time required by Developer in accordance with Developer’s construction schedule, apply for all such other permits and approvals as may be required by other governmental or quasigovernmental entities in connection with the development of, or the provision of services to, the Project. Developer shall also pay all required fees, including Other Agency Fees, when due to such public agencies. Developer acknowledges that City does not control the amount of any such fees. City shall reasonably cooperate with Developer in Developer’s effort to obtain such permits and approvals; provided, however, City shall have no

7.f
October 23, 2023 Packet Pg. 113
11 obligation to incur any costs, without compensation or reimbursement by Developer, or to amend any policy, regulation or ordinance of City in connection therewith.

3.4 Life of Project Approvals; Termination.

3.4.1 Generally. Except as otherwise expressly provided herein, the term of any and all Project Approvals shall automatically be extended for the longer of the Term of this Agreement or the term otherwise applicable to such Project Approvals, subject to the provisions of this Section 3.4. The termination of this Agreement at the end of the Term set forth in Section 2.2.1 shall have no effect on the Project Approvals, subject to the provisions in Section 3.4.2 below; provided, however, if this Agreement is terminated by either Party before expiration of the Term other than by Developer due to a Default by City, this Agreement and all Project Approvals shall terminate and have no further force or effect.

3.4.2 Continuing Vested Rights. In order to address and clarify Developer’s ability to build and operate the Project after the Expiration Date if not yet completed, the Parties agree that the following terms shall govern Developer’s vested rights. (a) Provided Developer has satisfied all its obligations under this Agreement as of the Expiration Date and termination of this Agreement, and Developer has obtained a final Certificate of Occupancy for the Project, the Project Approvals shall continue in effect as required for operation and use of the Project, subject only to California law that may apply to continued reliance on such approvals.
(b) If development of the Project has not been completed as of the Expiration Date and termination of this Agreement, Developer may continue work after such termination and may complete the Project as approved by the Project Approvals so long as the following conditions are satisfied:
(i) As of the Expiration Date Developer is not in Default, or if subject to a breach that has not yet been cured then Developer may not exercise its rights under this Section 3.4.2(b) unless and until it timely cures the breach in the reasonable judgment of City; (ii) As of the Expiration Date, physical site work has commenced and qualifies for vesting under California common law established by Avco Community Builders v. South Coast Regional Commission, 17 Cal.3rd 785 (1976), provided such work does not stop for six (6) consecutive months or longer; and
(iii) As of the Expiration Date, Developer has satisfied all applicable mitigation measures and conditions of approval adopted by City as part of the Project Approvals that have come due as and when required.

7.f
October 23, 2023 Packet Pg. 114
12 (c) If Developer fails to satisfy all conditions under Section 3.4.2(b) by the Expiration Date, the following shall apply with regard to future development or operation of the Project:
(i) Developer’s vested rights secured by this Agreement with regard to the Project shall terminate and all Project Approvals shall be deemed terminated and may not be relied on by Developer or the Project, notwithstanding any ability under Applicable City Regulations that may provide for extensions of the Project Approvals; and (ii) Developer shall have no vested right to construct or continue construction of the Project without first obtaining new City discretionary approvals then required.
(d) The terms and conditions of this Section 3.4.2 and their enforcement shall survive expiration or termination of this Agreement.

3.5 Initiatives. If any New City Law is enacted or imposed by a citizen-sponsored initiative or referendum, which New City Law would conflict with the Project Approvals or this Agreement or reduce the development rights or assurances provided by this Agreement, such New City Law shall not apply to the Property or Project; provided, however, the Parties acknowledge that City’s approval of this Agreement is a legislative action subject to referendum. Without limiting the generality of the foregoing, no moratorium or other limitation (whether relating to the rate, timing, phasing or sequencing of development) affecting any entitlements or permits to use that are approved or to be approved, issued or granted by City shall apply to the Property or Project. Developer agrees and understands that City does not have authority or jurisdiction over any other public agency’s ability to grant governmental approvals or permits or to impose a moratorium or other limitations that may affect the Project. City shall reasonably cooperate with Developer and, at Developer’s expense, undertake such actions as may be necessary to ensure this Agreement remains in full force and effect. City, except to submit to vote of the electorate initiatives and referendums required by law to be placed on a ballot and fulfill any legal responsibility to defend a ballot measure passed by its voters, shall not support, adopt or enact any New City Law, or take any other action which would violate the express provisions or spirit and intent of this Agreement.

3.6 No Affirmative Obligation to Develop; Timing of Development. The City acknowledges and agrees that the Developer has no affirmative obligation to develop the Project.

However, if the Developer, in its sole discretion, opts to develop the Project, such development shall comply with this Agreement. However, and not in any limitation of any of the foregoing, since the California Supreme Court held in Pardee Construction Co. v.

City of Camarillo, 37 Cal.3d 465 (1984), that the failure of the parties therein to consider, and expressly provide for, the timing of development resulted in a later-adopted initiative restricting the timing of development to prevail over such parties’ agreement, it is the desire of the Parties hereto to avoid that result. Therefore, notwithstanding the adoption of an initiative after the Effective Date by City’s electorate to the contrary, the Parties acknowledge that, except as otherwise provided for in this Agreement or the Existing

7.f
October 23, 2023 Packet Pg. 115
13 Approvals, Developer shall have the vested right to develop the Project in such order and at such rate and at such times as Developer deems appropriate in the exercise of its business judgment.

3.7 No Conflicting Enactments. Except as otherwise provided in this Agreement, City shall not impose on the Project (whether by action of the City Council or by initiative, referendum or other means) any New City Law that is in conflict with this Agreement or the Existing Approvals. Without limiting the generality of the foregoing, the City shall not (i) apply to the Property any change in land use designation or permitted use of the Property; (ii) limit or control the ability to obtain public utilities, services, or facilities; (iii) limit or control the uses; building setbacks, square footage, dimensions, floor plates, height; or location of buildings and structures; or spacing between buildings in a manner that is inconsistent with or more restrictive than the limitations included in the Existing Approvals or this Agreement; or (iv) limit or control the rate, timing, or sequencing of the approval, development or construction of all or any part of the Project or Existing Approvals, except as otherwise provided in this Agreement or the Existing Approvals.

3.8 Changes in the Law. As provided in Section 65869.5 of the Development Agreement Statute, this Agreement shall not preclude the applicability to the Project of changes in laws, regulations, plans or policies, to the extent that such changes are specifically mandated and required by changes in State or Federal laws or by changes in laws, regulations, plans or policies of special districts or other governmental entities, other than the City, created or operating pursuant to the laws of the State of California (“Changes in the Law”). In the event Changes in the Law prevent or preclude compliance with one or more provisions of this Agreement, the Parties shall meet and confer in good faith in order to determine whether such provisions of this Agreement shall be modified or suspended, or performance thereof delayed, as may be necessary to comply with Changes in the Law, and City and Developer shall agree to such action as may be reasonably required. Nothing in this Agreement shall preclude Developer from contesting by any available means (including administrative or judicial proceedings) the applicability to the Project of any such Changes in the Law.

3.9 No Reservation of Sanitary Sewer or Potable Water Capacity. City has found the Project to be consistent with the General Plan which anticipates that there will be sufficient potable water and sanitary sewer capacity to serve future development contemplated by the General Plan, including the Project. However, nothing in this Agreement is intended to exempt the Project or the Property from any water use rationing requirements that may be imposed on a City-wide basis from time to time in the future or be construed as a reservation of any existing sanitary sewer or potable water capacity. Nonetheless, to the maximum extent permitted by law and consistent with its authority, City upon Developer’s request shall cooperate with Developer (at no expense to City) in Developer’s effort to reserve such capacity for sewer and water services as may be necessary to serve the Project.

7.f
October 23, 2023 Packet Pg. 116
14 ARTICLE 4

FEES AND OTHER CHARGES

4.1 City Fees.

4.1.1 Impact Fees. Developer shall, for the first five (5) years of the Term, pay when due all existing Impact Fees as shown on Exhibit B at the rates in effect as of the Effective Date, except as increased pursuant to the escalation provisions in effect as of the Effective Date, and shall not be required to pay any Impact Fee enacted or established after the Effective Date or any increase in such existing Impact Fees.

Thereafter, and during the remainder of the Term (as it may be extended), Developer shall pay all original and any new Impact Fees at the rates in effect at the time due. The Impact Fees itemized on Exhibit B represent the Parties’ good faith effort to identify the Impact Fees applicable to the Project. City and Developer agree to amend and restate Exhibit B, as necessary, in the event one or more Impact Fees have been inadvertently omitted or if any cost or credit amounts have been inadvertently miscalculated.

4.1.2 All Other City Fees. Except as otherwise provided in Section 4.1.1 above as to Impact Fees, Developer agrees to pay when due any existing, new, increased or modified fees, including Processing Fees and Connection Fees, at the rates then in effect at the time land use or development permits, approvals or entitlements are applied for or issued on any or all portions of the Project so long as any new fees or increases in existing fees from the amount existing as of the Effective Date applies on a Citywide basis or applies to properties in the East Side Innovation District Vision Plan area and is consistent with the provisions of applicable California law, including the provisions of Government Code Section 66000 et seq.

4.1.3 Right to Protest. Developer acknowledges being aware of all City fees in effect as of the Effective Date that might be imposed on the Property and the Project, and Developer accepts and shall not protest or challenge imposition of the types and amounts of such fees in effect as of the Effective Date. Other than as specified in the previous sentence, Developer retains all rights to protest an imposition, fee, dedication, reservation, or other exaction, as set forth in California Government Code Section 66020, and nothing in this Agreement shall diminish or eliminate any of Developer’s rights set forth in such Section 66020. City may impose, and Developer shall comply with and not protest, those Exactions required by this Agreement and the Project Approvals.

4.2 Other Agency Fees. Nothing in this Agreement shall preclude City from collecting fees from Developer that are lawfully imposed on the Project by another agency having jurisdiction over the Project, which the City is required to collect on behalf of such other agencies (“Other Agency Fees”).

7.f
October 23, 2023 Packet Pg. 117
15 4.3 Taxes and Assessments. As of the Effective Date, assessments are in effect and applicable to the Property or the Project as shown on the latest property tax bill for the Property. City is not aware of any pending efforts to initiate or consider new or increased assessments that would apply to the Property or the Project. City may impose and Developer agrees to pay any and all existing, new, modified or increased taxes and assessments, other than Impact Fees, imposed on the Property or the Project in accordance with the laws in effect as of the date due, at the rate in effect at the time of payment. Nothing herein shall be construed so as to limit Developer from exercising whatever rights it may otherwise have in connection with protesting or otherwise objecting to the imposition of taxes or assessments on the Property; provided, Developer acknowledges being aware of all taxes and assessments in effect as of the Effective Date, and Developer accepts and agrees that it shall not protest or challenge their imposition on the Property and the Project. In the event an assessment district is lawfully formed to provide funding for services, improvements, maintenance or facilities which are substantially the same as those services, improvements, maintenance or facilities being funded by the fees or assessments to be paid by Developer under the Project Approvals or this Agreement, then at City’s election, taking into consideration City’s expectations as to when it would receive Developer’s payment of such fees or assessments, either (a) the fees or assessments to be paid by Developer shall be subject to reduction/credit in an amount equal to Developer’s new or increased assessment under the assessment district, or (b) the new assessment district shall reduce/credit Developer’s new assessment in an amount equal to such fees or assessments to be paid by Developer under the Project Approvals or this Agreement.

ARTICLE 5

DEVELOPER COMMUNITY BENEFITS COMMITMENTS

5.1 Public Benefits. Developer shall perform and provide the public benefit obligations described in this Section 5.1 in consideration for the rights and benefits conferred by City to Developer under this Agreement, which exceed those dedications, conditions, and exactions that may be imposed under Applicable Law.

5.1.1 POPA Easement. Prior to the issuance of final Certificate of Occupancy for the Project, Developer shall execute and record an easement and maintenance agreement providing for public access to both (1) the approximately 5,000 square foot portion of the central outdoor plaza located between the gate and Old County Road (“Front Plaza”) and (2) the approximately 12,000 square foot amenity courtyard between the buildings (“Courtyard”), each as shown in the Project Approvals and maintenance of the Front Plaza and Courtyard by Developer, in substantially the form attached hereto as Exhibit D (“POPA Easement”). The POPA Easement shall require Developer to allow public access to the Courtyard during daylight hours (sunrise to sundown) and to the Front Plaza during the longer of daylight hours (sunrise to sundown) or the hours that the tenant of the Community Benefit Space is open to the public, subject to the Developer’s reasonable rules and regulations related to safety, maintenance, and repairs, as well as improvements/renovations that meet the spirit and intent of the POPA Easement and subject to the reasonable approval of the Community Development Director.

7.f
October 23, 2023 Packet Pg. 118
16 The POPA Easement shall allow Developer to temporarily exclude the public or temporarily limit public access to portions of the Front Plaza and/or Courtyard if necessary to address safety concerns and perform maintenance and repairs to improvements within or immediately adjacent to the Front Plaza and to allow a reasonable limited number of private events per year for tenants of the Project and for non-profit or community events. The POPA Easement shall require Developer to maintain the Front Plaza and Courtyard at all times and indemnify and hold City harmless from any and all Claims arising from or relating to the design, construction, or maintenance of the Front Plaza and the public’s use thereof. The POPA Easement shall terminate in the event that (i) the Project is demolished or (ii) the Project undergoes a substantial change that is not already permitted under the Project Approvals and public access cannot be maintained by modifying the boundaries of the Front Plaza and Courtyard, provided that the POPA Easement shall not terminate in the event of demolition and reconstruction of any building or buildings in the Project following a casualty.

5.1.2 Recycled Water Pipe. At the time of issuance of a certificate of occupancy, the water infrastructure for the Project shall include dual plumbing for potable and recycled water, with separate pipe lines composed of appropriate material to accommodate recycled water.

5.2 Community Benefits.

5.2.1 Developer shall design and construct the improvements for the Project listed below and pay the following amounts listed below (“Community Benefits”) in exchange for the approval of the Planned Development zoning designation and a Planned Development Plan that allow Developer to construct buildings with a greater height and Floor Area Ratio than permitted under the Property’s previous Heavy Industrial zoning designation. These approvals have a value of Fourteen Million Dollars ($14,000,000). The Parties agree that the Community Benefits have a value of Seven Million Six Hundred Ninety Thousand Dollars ($7,690,000). (a) Design and construction of a space to be occupied by a Restaurant/Coffee Shop (or other Community Benefit Use pursuant to Section 5.2.4 below):
• Approximately 1,500 square feet
• Value: $555,000
(b) Design and construction of a Bike/Pedestrian Path as shown in the Project Approvals:
• Approximately 4,240 square feet
• Value: $148,400
(c) Provide public parking on nights, weekends, and federal holidays on the surface parking lot.

7.f
October 23, 2023 Packet Pg. 119
17 • Approximately 46 parking spaces
• Value: $690,000
(d) Addition of one dual head electric vehicle charging hub to provide two (2) charging stations on the surface parking lot.
(e) Designate seven (7) parking spaces for use by persons visiting the Community Benefit Space (defined below), Front Plaza, and/or Courtyard during the hours that any of the Community Benefit Space (defined below), Front Plaza, and/or Courtyard are open to the public, in addition to the times described in (c).
(f) Payments:
• Green Energy Efficiency & Sustainability Fund- $500,000 • Community Improvement & Recreation Fund - $3,000,000
• Downtown Improvements Fund - $2,796,000

5.2.2 Design and Construction of Community Benefit Space and Bike/Pedestrian Path.

The Community Benefit Space (defined in Section 5.2.4) and Bike/Pedestrian Path referenced in Section 5.2.1 shall be designed and submitted for approval as part of the Project building permit application, and shall be constructed in substantial conformance with the Project Approvals. The Parties shall enter into a Subdivision Improvement Agreement with respect to the Bike/Pedestrian Path and any work related to the Bike/Pedestrian Path that occurs on public property will be a public work subject to Prevailing Wage Laws.

5.2.3 Timing of Payments. The payments set forth in Section 5.2.1(c) shall be made in full prior to the issuance of the first building permit for the Project.

5.2.4 Community Benefit Space Timing. The South Phase building shown in the Project Approvals (“South Building”) shall include space suitable for a Restaurant/Coffee Shop Use or Community Benefit Use (“Community Benefit Space”). The final certificate of occupancy for the South Building must be requested (except as provided in this Section 5.2.4) and issued prior to the issuance of a final certificate of occupancy for any other building or structure in the Project. In the event that Developer has commenced construction of the South Building and a final certificate of occupancy for any other building or structure is requested by the Developer, the Developer will deposit $555,000 with the City which shall be returned in full without interest to the Developer upon issuance of the final certificate of occupancy for the South Building that includes the Community Benefit Space in compliance with this Agreement. In the event that the South Building has commenced construction under this Section, but does not receive its final certificate of occupancy within the Term (not including any extension of the Term), the $555,000 shall become non-refundable and the City shall elect to deposit the $555,000 in one or more of the funds described in Section 5.2.1(c) above, and Developer will have no further obligations related to the Restaurant/Coffee Shop space Community

7.f
October 23, 2023 Packet Pg. 120
18 Benefit Space and can use the space Community Benefit Space for any permitted purpose.

5.2.5 Community Benefit Space Tenant Improvements and Marketing Efforts. Developer shall construct or pay all costs associated with completion of the Community Benefit Space to an “Initial Shell Condition” as defined in Exhibit C prior to the issuance of a final certificate of occupancy for the South Building. The Parties acknowledge and agree that the intent is that the Community Benefit Space will be used for a Restaurant/Coffee Shop Use. The Developer will make good faith efforts to market and lease the Community Benefit Space to a tenant providing a Restaurant/Coffee Shop Use, but may also market the Community Benefit Space to other Community Benefit Uses (“Marketing and Leasing Efforts”) and will provide the City Community Development Director regular updates (not less than quarterly) on these Marketing and Leasing Efforts until a lease is entered into with a tenant. Developer or Assignee shall offer the Community Benefit Space at an initial triple net rent rate that does not exceed a fair market rent rate consistent with this Agreement. Developer or Assignee will promptly notify City when a tenant providing a Community Benefit Use has executed a lease of the Community Benefit Space. If a lease is not entered into, and there are no active negotiations likely to lead to a lease, despite good faith Marketing and Leasing Efforts within three (3) years of the final Certificate of Occupancy for the South Building, and after a good faith meet and confer by the Parties, the Developer shall pay a community amenity fee in the amount of $555,000 to the City to use for any purpose the City deems appropriate in its sole and absolute discretion and the Developer will have no further obligations related to the Community Benefit Space and can use the Community Benefit Space for any permitted purpose. In the event the initial tenant’s lease term is less than ten (10) years or terminates in less than ten (10) years, the Developer’s obligations hereunder to make Marketing and Leasing Efforts to enter into a new lease consistent with this Agreement and provide regular updates to the City Community Development Director shall continue until the date that is ten (10) years from issuance of the final Certificate of Occupancy for the South Building (“Initial Leasing Period”). After the Initial Leasing Period, the Developer will have no further obligations related to the Community Benefit Space and can use the Community Benefit Space for any permitted purpose. This Section

5.2.5 shall survive termination of this Agreement through the Initial Leasing Period.

5.2.6 Public Parking and EV Charging Stations. Developer shall designate the surface parking lot, consisting of approximately forty-six (46) spaces, as available for use by the public at no cost during the hours of 6 p.m. to 11 p.m. Monday through Friday and from 7:00 a.m. to 11:00 p.m. on weekends and federal holidays. Prior to the issuance of a Certificate of Occupancy for the South Building, the Parties shall enter into a Public Parking Agreement in substantially the form attached hereto as Exhibit E to document Developer’s obligation to provide public parking.

Developer shall also provide one dual head electric vehicle charging hub to create two (2) charging stations and designate two (2) parking spaces in the surface parking lot for vehicles using the charging stations. The charging stations shall be available for use by the public during the same hours as the other spaces in the

7.f
October 23, 2023 Packet Pg. 121
19 surface parking lot. The public parking spaces available nights and weekends, the seven (7) parking spaces available for use by visitors of the Front Plaza, Courtyard, or Community Benefit Space, and the two (2) parking spaces with charging stations shall be in substantially the locations shown on the conceptual plan attached hereto as Exhibit G.

ARTICLE 6

ANNUAL REVIEW

6.1 Periodic Review.

6.1.1 As required by the City of San Carlos City Code Section 18.37.080, Developer shall be required to demonstrate compliance with the provisions of the Agreement at least once a year at which time the Community Development Director shall review the Agreement.

6.1.2 The annual review shall be conducted as provided herein:
(a) Documentation of Compliance. By the last business day of January of each year, the Developer shall provide documentation of its compliance with the Agreement during the previous calendar year. Promptly upon receipt of Developer’s documentation of compliance, the City’s Community Development Director shall review the documentation and determine, on the basis of substantial evidence, whether the Developer has complied with the provisions of this Agreement.
(b) Finding of Compliance. If the Community Development Director, on the basis of substantial evidence, finds compliance by Developer with the provisions of this Agreement, the Community Development Director shall issue a finding of compliance, which shall be in recordable form and may be recorded with the County Recorder after conclusion of the review. (c) Finding of Noncompliance. If the Community Development Director finds Developer has not complied with the provisions of this Agreement, the Community Development Director may issue a finding of noncompliance which may be recorded by the City with the County Recorder after it becomes final. The Community Development Director shall specify in writing to Developer the respects in which applicant has failed to comply, and shall set forth terms of compliance and specify a reasonable time for Developer to meet the terms of compliance.

7.f
October 23, 2023 Packet Pg. 122
20 (d) Appeal of Determination. Within seven days after issuance of a finding of compliance or a finding of noncompliance, any interested person may file a written appeal of the finding with the City Council. The appellant shall pay fees and charges for the filing and processing of the appeal in amounts established by resolution of the City Council. The appellant shall specify the reasons for the appeal. The issuance of a finding of compliance or finding of noncompliance by the Community Development Director and the expiration of the appeal period without appeal, or the confirmation by the City Council of the issuance of the finding on such appeal, shall conclude the review for the applicable period and such determination shall be final. (Ord. 1438 § 4 (Exh. A (part)), 2011
(e) If after City’s determination becomes final pursuant to subsection(d) Developer does not comply with any terms of compliance within the prescribed time limits, the Parties may terminate or modify the Agreement by mutual consent or the Director may refer this Agreement to the City Council for termination or modification and the City Council shall conduct a public hearing. After the public hearing, the City Council may terminate this Agreement, modify the finding of noncompliance and specify a reasonable time for Developer to meet the terms of compliance, or rescind the finding of noncompliance and issue a finding of compliance. If the City Council modifies the finding of noncompliance and the Developer does not meet the terms of compliance within the prescribed time limits, the Community Development Director shall issue a notice of termination in accordance with section 11.3.

6.2 Certificate of Good Faith Compliance. If, after an annual review, City finds Developer has complied in good faith with the material terms of this Agreement, City shall within ten (10) days after receiving a request from Developer issue to Developer a certificate of compliance certifying that Developer has so complied through the period of the applicable annual review.

6.3 No Waiver. Failure of City to conduct an annual review shall not constitute a waiver by City of its rights to otherwise enforce the provisions of this Agreement nor shall Developer have or assert any defense to such enforcement by reason of any such failure to conduct an annual review.

6.4 Reimbursement of Annual Review Costs. Developer shall pay the City for the reasonable costs incurred, including charges for City Attorney and other City staff time, in conducting its annual review of the Agreement within thirty (30) days of receipt of an invoice therefore.

Reimbursement shall be based on City’s charges for City Attorney and staff time billed for legal review and development project application review pursuant to City’s fee schedule in effect at the time.

7.f
October 23, 2023 Packet Pg. 123
21 ARTICLE 7

MORTGAGEE PROTECTION

7.1 Mortgagee Protection. This Agreement shall be superior and senior to any lien placed upon the Property or any portion thereof after the date of recording the Agreement, including the lien of any deed of trust or mortgage (“Mortgage”). Notwithstanding the foregoing, no breach hereof shall defeat, render invalid, diminish or impair the lien of any Mortgage made in good faith and for value, but all of the terms and conditions contained in this Agreement shall be binding upon and effective against and shall run to the benefit of any person or entity, including any deed of trust beneficiary or mortgagee (“Mortgagee”), who acquires title or possession to the Property, or any portion thereof, by foreclosure, trustee’s sale, deed in lieu of foreclosure or otherwise, subject to the provisions in Section 2.1 limiting the benefits of this Agreement to Developer and its successors but not a separate owner of the Property.

7.2 Mortgagee Not Obligated.

7.2.1 Notwithstanding the provisions of Section 7.1 above, except as specified in Section

7.2.2, no Mortgagee shall have any obligation or duty under this Agreement to construct or complete the construction of the Project, or any portion thereof, or to guarantee such construction or completion; provided, however, that a Mortgagee shall not be entitled to devote the Property to any use except in full compliance with the Project Approvals and this Agreement nor to construct any improvements thereon or institute any uses other than those uses and improvements provided for or authorized by this Agreement and the Project Approvals.

7.2.2 Any Mortgagee or successor in interest to a Mortgagee that is not proceeding to construct or complete construction of the Project pursuant to the Project Approvals and this Agreement must comply with all federal and state law and permit conditions applicable to the Project construction and shall not allow or permit a nuisance.

7.3 Notice of Default to Mortgagee; Right to Cure. With respect to any Mortgage granted by Developer as provided herein, so long as any such Mortgage shall remain unsatisfied of record, the following provisions shall apply:

7.3.1 City, upon serving Developer any notice of Default, shall also serve a copy of such notice upon any Mortgagee at the address provided to City, and no notice by City to Developer hereunder shall affect any rights of a Mortgagee unless and until a copy thereof has been so served on such Mortgagee; provided, however, that failure so to deliver any such notice shall in no way affect the validity of the notice sent to Developer as between Developer and City. In the event of a Default by Developer, any Mortgagee shall have the right to remedy, or cause to be remedied, such Default within sixty (60) days following the later to occur of (i) the date of Mortgagee’s receipt of the notice referred to in Section 7.3.1 above, or (ii) the expiration of the period provided herein for Developer to remedy or cure such Default, and City shall

7.f
October 23, 2023 Packet Pg. 124
22 accept such performance by or at the insistence of the Mortgagee as if the same had been timely made by Developer; provided, however, that (a) if such Default is not capable of being cured within the timeframes set forth in this Section 8.3.2 and Mortgagee commences to cure the Default within such timeframes, then Mortgagee shall have such additional time as is required to cure the Default so long as Mortgagee diligently prosecutes the cure to completion and (b) if possession of the Property (or portion thereof) is required to effectuate such cure or remedy, the Mortgagee shall be deemed to have timely cured or remedied if it commences the proceedings necessary to obtain possession thereof within sixty (60) days after receipt of the copy of the notice, diligently pursues such proceedings to completion, and, after obtaining possession, diligently completes such cure or remedy.

7.3.2 Any notice or other communication which City shall desire or is required to give to or serve upon the Mortgagee shall be in writing and shall be served in the manner set forth in Section 12.5, addressed to the Mortgagee at the address provided by Mortgagee to City. Any notice or other communication which Mortgagee shall give to or serve upon City shall be deemed to have been duly given or served if sent in the manner and at City’s address as set forth in Section 12.5, or at such other address as shall be designated by City by notice in writing given to the Mortgagee in like manner.

7.4 No Supersedure. Nothing in this Article 7 shall be deemed to supersede or release a Mortgagee or modify a Mortgagee’s obligations under any subdivision or public improvement agreement, temporary access agreement or other obligation incurred with respect to the Project outside this Agreement, nor shall any provision of this Article 7 constitute an obligation of City to such Mortgagee, except as to the notice requirements of Section 7.3.

7.5 Technical Amendments to this Article 7. City agrees to reasonably consider and approve interpretations and/or technical amendments to the provisions of this Agreement that are required by lenders for the acquisition and construction of the improvements on the Property or any refinancing thereof and to otherwise cooperate in good faith with Developer at Developer’s expense to facilitate Developer’s negotiations with lenders.

ARTICLE 8

AMENDMENT OF AGREEMENT AND PROJECT APPROVALS

8.1 Amendment of this Agreement.

8.1.1 Amendment of Agreement by Mutual Consent. Except as otherwise expressly provided herein (including but not limited to Section 6.1 relating to City’s annual review and Section 11.3 relating to termination in the event of a Default), this Agreement may be terminated, modified or amended in writing from time to time only by mutual consent of the Parties hereto or their successors-in-interest or assigns, and in accordance with the provisions of Government Code sections 65867, 65867.5 and 65868.

7.f
October 23, 2023 Packet Pg. 125
23 8.1.2 Refinement by Operating Memoranda.
(a) The Parties acknowledge that the provisions of this Agreement require a close degree of cooperation between City and Developer, and during the course of implementing this Agreement and developing the Project refinements and clarifications of this Agreement become appropriate and desired with respect to the details of performance of City and Developer. If and when, from time to time, during the Term of this Agreement, City and Developer agree that such a refinement is necessary or appropriate, City and Developer shall effectuate such refinement through a memorandum (the “Operating Memorandum”) approved in writing by City and Developer, which, after execution, shall be attached hereto as an addendum and become a part hereof. Any Operating Memorandum may be further refined from time to time as necessary with future approval by City and Developer. No Operating Memorandum shall constitute an amendment to this Agreement requiring public notice or hearing. The City Manager, in consultation with the City Attorney, shall make the determination on behalf of City whether a requested refinement may be effectuated pursuant to this Section 8.1.2 or whether the requested refinement is of such a character to constitute an amendment hereof pursuant to Section 8.1.3 below. The City Manager shall be authorized to execute any Operating Memoranda hereunder on behalf of City.
(b) Any amendment to this Agreement that, in the context of the overall Project contemplated by this Agreement that does not substantially affect (i) the Term; (ii) permitted uses of the Property; (iii) provisions for the reservation or dedication of land; (iv) conditions, terms, restrictions or requirements for Additional Project Approvals; (v) increases in the density or intensity of the use of the Property or the maximum height or size of proposed buildings; (vi) monetary contributions by Developer; or (vii) the provision of Community Benefits described in Article 5 shall be deemed an Insubstantial Amendment. The City Manager, except to the extent otherwise required by Applicable Law, may approve the Insubstantial Amendment without notice and public hearing.

8.1.3 Agreement Amendments. Any revision to this Agreement which is determined not to qualify for an Operating Memorandum as set forth in Section 8.1.2 shall be deemed an “Agreement Amendment” and shall require giving of notice and a public hearing before the Planning Commission and City Council in accordance with Applicable Law. The City Manager shall have the authority in her or her reasonable discretion to determine if a proposed revision is an Agreement Amendment subject to this Section 8.1.3 or qualifies for an Operating Memorandum subject to Section 8.1.2.

8.1.4 Requirement for Writing. No modification, amendment or other change to this Agreement or any provision hereof shall be effective for any purpose unless

7.f
October 23, 2023 Packet Pg. 126
24 specifically set forth in writing which refers expressly to this Agreement and is signed by duly authorized representatives of each Party or their successors.

8.2 Amendments to Development Agreement Statute. This Agreement has been entered into in reliance upon the provisions of the Development Agreement Statute as those provisions existed as of the date of execution of this Agreement. No amendment or addition to those provisions which would materially affect the interpretation or enforceability of this Agreement shall be applicable to this Agreement, unless such amendment or addition is specifically required by the California State Legislature, or is mandated by a court of competent jurisdiction. If such amendment or change is permissive (as opposed to mandatory), this Agreement shall not be affected by same unless the Parties mutually agree in writing to amend this Agreement to permit such applicability.

8.3 Amendments to Project Approvals.

8.3.1 Generally. Project Approvals (except for this Agreement the amendment process for which is set forth in this Article 8) may be amended or modified from time to time, but only at the written request of Developer or with the written consent of Developer at its sole discretion. All amendments to the Project Approvals shall automatically become part of the Project Approvals. The permitted uses of the Property, the maximum density, the intensity of use, the maximum height and size of the proposed buildings, provisions for reservation or dedication of land for public purposes, the conditions, terms, restrictions and requirements for subsequent discretionary actions, the provisions for public improvements and financing of public improvements, and the other terms and conditions of development as set forth in all such amendments shall be automatically vested pursuant to this Agreement, without requiring an amendment to this Agreement. Amendments to the Project Approvals shall be governed by the Project Approvals and the Applicable Laws. City shall not request or process any amendment to the Project Approvals that would affect the Property or the Project without Developer’s prior written consent.

8.3.2 Administrative Amendments of Project Approvals. Upon the request of Developer for an amendment or modification of any Project Approvals (except for this Agreement the amendment process for which is set forth in this Article 8), the City Manager or his or her designee shall determine, at his or her discretion and subject to referral to a hearing body if considered appropriate: (a) whether the requested amendment or modification is minor when considered in light of the Project as a whole; and (b) whether the requested amendment or modification substantially conforms with the material terms of this Agreement and the Applicable Laws and may be processed administratively. If the City Manager or his or her designee finds that the requested amendment or modification is both minor and substantially conforms with the material terms of this Agreement and the Applicable Laws, the amendment or modification shall be determined to be an “Administrative Project Amendment,” and the City Manager or his or her designee may approve the Administrative Project Amendment, without public notice or a public hearing.

Without limiting the generality of the foregoing, lot line adjustments, minor

7.f
October 23, 2023 Packet Pg. 127
25 reductions in the density, intensity, scale or scope of the Project, minor alterations in vehicle circulation patterns or vehicle access points, variations in the location of structures that do not substantially alter the design concepts of the Project, substitution of comparable landscaping for any landscaping shown on any development plan or landscape plan, variations in the location or installation of utilities and other infrastructure connections and facilities that do not substantially alter design concepts of the Project, and minor adjustments to a subdivision map or the Property legal description shall be deemed to be minor amendments or modifications. Any request of Developer for an amendment or modification to a Project Approval that is determined not to be an Administrative Project Amendment as set forth above shall be subject to review, consideration and action pursuant to the Applicable Laws and this Agreement.

8.4 Reliance on Initial Study and MND. The Initial Study and MND, which have been certified by City as being in compliance with CEQA, address the potential environmental impacts of the entire Project as it is described in the Project Approvals as described in the MMRP.

It is agreed that, in acting on any discretionary Additional Project Approvals for the Project, City will rely on the Initial Study and MND to satisfy the requirements of CEQA to the fullest extent permissible by CEQA, and City will not require a new initial study, negative declaration or subsequent or supplemental EIR unless City determines that such additional analysis and processing are required by CEQA and will not impose on the Project any mitigation measures or other conditions of approval other than those specifically imposed by the Project Approvals and the MMRP or specifically required by the Applicable Laws.

8.5 Subsequent CEQA Review. In the event that any additional CEQA documentation is legally required for any discretionary Additional Project Approval for the Project, then the scope of such documentation shall be focused, to the extent possible consistent with CEQA, on the specific subject matter of the Additional Project Approval, and City, at Developer’s expense, shall conduct such CEQA review as expeditiously as possible.

ARTICLE 9

COOPERATION AND IMPLEMENTATION

9.1 Additional Project Approvals. Certain subsequent land use approvals, entitlements, and permits other than the Existing Approvals, will be necessary or desirable for implementation of the Project (“Additional Project Approvals”). The Additional Project Approvals may include, without limitation, the following: amendments of the Project Approvals, grading permits, building permits, sewer and water connection permits, certificates of occupancy, lot line adjustments, site plans, development plans, land use plans, building plans and specifications, parcel maps and subdivision maps, and any amendments to, or repealing of, any of the foregoing. Except as otherwise expressly provided herein, the City shall not impose requirements or conditions upon Project development and construction that are inconsistent with the Existing Approvals and the terms and conditions of this Agreement. Further, except as expressly provided herein, City shall not exercise discretion in determining whether or how to grant Additional Project

7.f
October 23, 2023 Packet Pg. 128
26 Approvals in a manner that would prevent development of the Project for the uses and to the maximum intensity of development set forth in the Existing Approvals.

9.2 Scope of Review of Additional Project Approvals. By approving the Project Approvals, City has made a final policy decision that the Project is in the best interests of the public health, safety and general welfare. Accordingly, City shall not use its authority in considering any application for a discretionary Additional Project Approval to change the policy decisions reflected by the Project Approvals or otherwise to prevent or delay development of the Project as set forth in the Project Approvals. Instead, the Additional Project Approvals shall be deemed to be tools to implement those final policy decisions.

9.3 Processing Applications for Additional Project Approvals.

9.3.1 Developer acknowledges that City cannot begin processing applications for Additional Project Approvals until Developer submits complete applications on a timely basis. Developer shall use diligent good faith efforts to (i) provide to City in a timely manner any and all documents, applications, plans, and other information necessary for City to carry out its obligations hereunder; and (ii) cause Developer’s planners, engineers, and all other consultants to provide to City in a timely manner all such documents, applications, plans and other materials required under Applicable Laws. It is the express intent of Developer and City to cooperate and diligently work to obtain any and all Additional Project Approvals.

9.3.2 Upon submission by Developer of all appropriate applications and Processing Fees for any pending Additional Project Approval, City shall, to the full extent allowed by Applicable Laws, promptly and diligently, subject to City ordinances, policies and procedures regarding hiring and contracting, commence and complete all steps necessary to act on Developer’s currently pending Additional Project Approval applications including: (i) if legally required, providing notice and holding public hearings; and (ii) acting on any such pending Additional Project Approval application. Upon Developer’s request and prior approval, when City deems it necessary or desirable, City will endeavor to retain consultants to assist in reviewing and processing Developer’s applications, at Developer’s expense including any added expense for City staff to retain and supervise such consultants.

City similarly will consider Developer’s request to arrange overtime staff assistance; provided, Developer acknowledges that City will have other development applications and planning work in process or waiting to be processed from time to time, and Developer’s Additional Project Approval applications are not entitled to priority treatment to the disadvantage of such other applications and work; and provided further, Developer acknowledges there are practical constraints on City’s ability to arrange staff overtime.

9.4 Other Agency Additional Project Approvals; Authority of City. City shall cooperate with Developer, to the extent appropriate and as permitted by law, in Developer’s efforts to obtain, as may be required, Other Agency Additional Project Approvals. Notwithstanding the issuance to Developer of Other Agency Additional Project Approvals, Developer agrees that City shall have the right to review, modify, approve and/or reject any and all

7.f
October 23, 2023 Packet Pg. 129
27 submissions subject to the Other Agency Additional Project Approvals which, but for the authority of the other governmental or quasi-governmental entities issuing the Other Agency Additional Project Approvals, would otherwise require City approval. Developer agrees that City may review, modify, approve and/or reject any such materials or applications to ensure consistency with this Agreement and the Project Approvals and Developer shall incorporate any and all changes required by City prior to submitting such materials and applications to the other governmental or quasi-governmental entities for review and/or approval.

9.5 Implementation of Necessary Mitigation Measures and Conditions. Developer shall, at its sole cost and expense, comply with the MMRP requirements and conditions of approval included with the Project Approvals as applicable to the Property and Project.

9.6 Cooperation in the Event of Legal Challenge. City and Developer shall cooperate in the defense of any court action or proceeding instituted by a third party or other governmental entity or official challenging the validity of any provision of this Agreement or the City’s approval of this Agreement or any of the Project Approvals (each, a “Litigation Challenge”), and the Parties shall keep each other informed of all developments relating to such defense, subject only to confidentiality requirements that may prevent the communication of such information. Developer’s monetary obligations under this Section

9.6 and its subsections shall survive expiration or earlier termination of this Agreement.

9.6.1 Meet and Confer. If a Litigation Challenge is filed, upon receipt of the petition, the Parties will have twenty (20) days to meet and confer regarding the merits of such Litigation Challenge and to determine whether to defend against the Litigation Challenge, which period may be extended by the Parties’ mutual agreement so long as it does not impact any litigation deadlines. The City and Developer mutually commit to meet all required litigation timelines and deadlines. The Parties shall expeditiously enter a joint defense agreement, which will include among other things, provisions regarding confidentiality. The City Manager is authorized to negotiate and enter such joint defense agreement in a form acceptable to the City Attorney. Such joint defense agreement shall also provide that any proposed settlement of a Litigation Challenge shall be subject to City’s and Developer’s approval, each in its reasonable discretion. If the terms of the proposed settlement would constitute an amendment or modification of this Agreement, the settlement shall not become effective unless such amendment or modification is approved by Developer, and by City in accordance with Applicable Laws, and City reserves its full legislative discretion with respect thereto.

9.6.2 Defense Election. If, after meeting and conferring, the Parties mutually agree (each in its sole discretion) to defend against the Litigation Challenge, then the following shall apply:
(a) Joint Representation. For the purposes of cost-efficiency and coordination, the Parties shall first consider defending the Litigation Challenge jointly, with counsel and under terms of joint representation mutually acceptable to

7.f
October 23, 2023 Packet Pg. 130
28 the City and Developer (each in its sole discretion), at the Developer’s sole cost and expense.
(b) If the Parties cannot reach timely and mutual agreement on a joint counsel, and Developer continues to elect (in its sole discretion) to defend against the Litigation Challenge, then:
(i) Developer shall take the lead role defending such Litigation Challenge and may, in its sole discretion, elect to be represented by the legal counsel of its choice;
(ii) City may, in its sole discretion, elect to be separately represented by the outside legal counsel of its choice in any such action or proceeding with the reasonable costs of such representation to be paid by Developer;
(iii) Developer shall reimburse City, within ten (10) business days following City’s written demand therefor, which may be made from time to time during the course of such litigation, all necessary and reasonable costs incurred by City in connection with the Litigation Challenge, including City’s administrative, outside legal fees and costs, and court costs;
(iv) The Parties intend that the City’s role under subsection (b)(ii) shall be primarily oversight although the City reserves its right to protect the City’s interests, and the City shall make good faith efforts to maximize coordination and minimize its outside legal costs (for example, minimizing filing separate briefs, and duplication of effort to the extent feasible).
(v) For any Litigation Challenge which the Developer has elected to defend under this Section 9.6.2(b) Developer shall indemnify, defend, and hold harmless the City and the City Parties from any liability, damages, claim, action, cause of action, judgment (including City costs to effectuate such judgment, including any attorneys’ fees or cost awards, including attorneys’ fees awarded under Code of Civil Procedure Section 1021.5, assessed or awarded against City by way of judgment, settlement, or stipulation), loss (direct or indirect), obligation, order, fine, penalty or proceeding (including legal costs, attorneys’ fees, expert witness or consultant fees, staff time, expenses or costs) related to such Litigation Challenge. “Attorneys’ fees” as used in this Section 9.6.2(b)(v) shall include reasonable City Attorney’s time as a pass-through cost without markup.

9.6.3 Developer Election Not To Defend. If Developer elects, in its sole and absolute discretion, not to defend against the Litigation Challenge, it shall deliver written

7.f
October 23, 2023 Packet Pg. 131
29 notice to the City regarding such decision. If Developer elects not to defend, the City has the right, but not the obligation, to proceed to defend against the Litigation Challenge and shall take the lead role defending such Litigation Challenge and may, in its sole discretion, elect to be represented by the legal counsel of its choice, at its sole cost and expense. If Developer elects not to defend, the City has the right, but not the obligation, to terminate this Agreement and any Project Approvals then in effect, and to consider the Developer’s application for any Additional Project Approvals withdrawn. In the event the City does not terminate this Agreement, then if the terms of a proposed settlement would constitute an amendment or modification of this Agreement, the settlement shall not become effective unless such amendment or modification is approved by Developer, and by City in accordance with Applicable Laws, and City reserves its full legislative discretion with respect thereto. In the event the Developer does not approve such amendment or modification, the City retains the right, but not the obligation, to terminate this Agreement and any Project Approvals then in effect, and to consider the Developer’s application for any Additional Project Approvals withdrawn. If Developer elects pursuant to this Section 9.6.3 not to defend against the Litigation Challenge and so notifies City, and City thereafter elects not to defend against the Litigation Challenge, Developer shall be liable for and shall promptly reimburse City for (i) any costs, fees or payments owed as a result of the Litigation Challenge that may be City’s obligation, whether by judgment, settlement or otherwise, and (ii) all necessary and reasonable costs incurred by City in connection with the Litigation Challenge, including City’s administrative, outside legal fees and costs, and court costs.

9.7 Revision to Project. In the event of a court order issued as a result of a successful Litigation Challenge, City shall, to the extent permitted by law or court order, in good faith seek to comply with the court order in such a manner as will maintain the integrity of the Project Approvals and avoid or minimize to the greatest extent possible (i) any impact to the development of the Project as provided for in, and contemplated by, the Project Approvals, or (ii) any conflict with the Project Approvals or frustration of the intent or purpose of the Project Approvals.

9.8 State, Federal or Case Law. Where any state, federal or case law allows City to exercise any discretion or take any act with respect to that law, City shall, in an expeditious and timely manner, at the earliest possible time, (a) exercise its discretion in such a way as to be consistent with, and carry out the terms of, this Agreement and (b) take such other actions as may be necessary to carry out in good faith the terms of this Agreement.

9.9 Compliance with Laws. Developer, at its sole cost and expense, shall comply with the requirements of, and obtain all permits and approvals required by local, State and Federal agencies having jurisdiction over the Property or Project. Furthermore, Developer shall carry out the Project work in conformity with all Applicable Laws including, if and to the extent applicable, all State Labor Code requirements and implementing regulations of the Department of Industrial Relations pertaining to “public works,” including the payment of prevailing wages (collectively, “Prevailing Wage Laws”). Developer shall require the contractor(s) for all work that is subject to Prevailing Wage Laws to submit, upon request

7.f
October 23, 2023 Packet Pg. 132
30 by City, certified copies of payroll records to City at the Property or at another location within City, and to maintain and make records available to City and its designees for inspection and copying to ensure compliance with Prevailing Wage Laws. Developer shall also include in each of its contractor agreements, a provision in form reasonably acceptable to City, obligating the contractor to require its contractors and/or subcontractors to comply with Prevailing Wage Laws and to submit, upon request by City, certified copies of payroll records to City and to maintain and make such payroll records available to City and its designees for inspection and copying during regular business hours at the contractor’s or subcontractor’s regular place of business. Developer shall defend (with counsel reasonably acceptable to the City), indemnify, assume all responsibility for, and hold harmless City Parties from and against any and all present and future Claims arising out of or in any way connected with Developer’s or its contractors’ or subcontractors’ obligations to comply with all Prevailing Wage Laws, including all Claims that may be made by contractors, subcontractors or other third-party claimants pursuant to Labor Code sections 1726 and 1781. Nothing herein is intended to require compliance with Prevailing Wage Laws beyond what is required by law. Developer hereby waives and releases City Parties from any and all manner of Claims or other compensation whatsoever, in law or equity, of whatever kind or nature, whether known or unknown, direct or indirect, foreseeable or unforeseeable, absolute or contingent, now existing or which may in the future arise, including lost business opportunities or economic advantage, and special and consequential damages, arising out of, directly or indirectly, or in any way connected with Developer’s obligation to comply with all Prevailing Wage Laws. Developer is aware of and familiar with the provisions of Section 1542 of the California Civil Code which provides as follows:
“A GENERAL RELEASE DOES NOT EXTEND TO CLAIMS WHICH THE

CREDITOR OR RELEASING PARTY DOES NOT KNOW OR SUSPECT TO

EXIST IN HIS OR HER FAVOR AT THE TIME OF EXECUTING THE

RELEASE AND THAT, IF KNOWN BY HIM OR HER, WOULD HAVE

MATERIALLY AFFECTED HIS OR HER SETTLEMENT WITH THE
DEBTOR OR RELEASED PARTY.”
INITIALS: DEVELOPER ____________
As it relates to this Section 9.9, Developer hereby waives and relinquishes all rights and benefits which it may have under Section 1542 of the California Civil Code.

9.10 Indemnity and Hold Harmless. Developer shall indemnify, defend (with counsel reasonably acceptable to City) and hold harmless the City, including its elected and appointed officers, officials, employees, contractors, representatives and authorized agents (each a “City Party” and collectively “City Parties”) from and against any and all Claims, including Claims for any bodily injury, death, or property damage, resulting directly or indirectly from the development or construction of the Project, and, if applicable from compliance with the terms of this Agreement, and/or from any other acts or omissions of Developer under this Agreement, whether such acts or omissions are by Developer or any of Developer’s contractors, subcontractors, agents or employees (each a “Developer Party” and collectively “Developer Parties”); provided that Developer’s obligation to indemnify and hold harmless (but not Developer’s duty to defend) shall be limited (and

7.f
October 23, 2023 Packet Pg. 133
31 shall not apply) to the extent such Claims are found to arise from the gross negligence or willful misconduct of a City Party. Developer shall further indemnify, defend (with counsel reasonably acceptable to City) and hold harmless the City Parties from and against any and all Claims arising from or related to any Developer Party’s failure to comply with any Applicable Laws, including without limitation Prevailing Wage Laws. Developer’s obligations under this Section 9.10 shall survive expiration or earlier termination of this Agreement.

9.11 Sales Tax Point of Sale Designation. The Developer shall use good faith, diligent efforts to the extent allowed by law to require all persons and entities providing materials to be used in connection with the construction and development of, or incorporated into, the Project, including by way of illustration but not limitation bulk lumber, concrete, structural steel, roof trusses and other pre- fabricated building components, to (a) obtain a use tax direct payment permit; (b) elect to obtain a subcontractor permit for the job site of a contract valued at $5 Million Dollars or more; or (c) otherwise designate the Property as the place of use of material used in the construction of the Project and the place of sale of all fixtures installed in and/or furnished in order to have the local portion of the sales and use tax distributed directly to City instead of through the county-wide pool. Developer shall instruct its general contractor(s) for the Project to, and shall cause such general contractor(s) to instruct its/their subcontractors to, cooperate with City to ensure the local sales/use tax derived from construction of the Project is allocated to City to the fullest extent possible and to the extent allowed by law. This Section 9.11 shall not apply to tenants who perform their own tenant improvement work.

9.11.1 To assist City in its efforts to ensure that such local sales/use tax is so allocated to City, Developer shall on an annual basis, or as frequently as quarterly upon City’s request, provide City with such information as shall be reasonably requested by City regarding subcontractors working on the Project with contracts in excess of the amount set forth above, including a description of all applicable work and materials and the dollar value of such subcontracts, and, if applicable, evidence of their designation, such as approvals or applications for the direct payment permit, of City as the place of use of such work and materials. City may use such information to contact each subcontractor who may qualify for local allocation of use taxes to City. Notwithstanding the foregoing, the failure of any general contractor(s) or subcontractor(s) to allocate sales and use tax revenues as provided herein or to comply with this Section 9.11 shall not constitute a breach by Developer under this Agreement.

ARTICLE 10

ASSIGNMENT

10.1 Transfers. Prior to the issuance of a final Certificate of Occupancy for the Project, neither City nor Developer may assign its rights or delegate its duties under this Agreement, except for Developer Permitted Transfers as defined below, without the express written consent of the other Party, which consent will not be unreasonably withheld or delayed. Developer shall provide the City with written notice of any proposed transfer or assignment of

7.f
October 23, 2023 Packet Pg. 134
32 Developer’s rights or obligations hereunder at least thirty (30) days prior to such Assignment and request City’s consent to such transfer, as provided herein. Each such notice of proposed transfer shall be accompanied by reasonable (non-confidential) evidence of the corporate, limited liability company or other legal entity’s existence and good standing, experience with similar projects, and financial resources. City may refuse to give consent to a proposed transfer only if, in light of the proposed transferee’s reputation, experience with similar projects, and/or financial resources, such transferee would not, in City’s reasonable opinion, be able to perform the obligations proposed to be assumed by such transferee, and such determinations will be made by the City Manager.

Prior to any transfer, the Developer and assignee shall enter into an assignment and assumption agreement in substantially the form of Exhibit F (“Assignment and Assumption Agreement”), and subject to prior approval, which shall not be unreasonably withheld or delayed, of the City Manager and the City Attorney. So long as City has not provided Developer notice of breach before or during City’s review of Developer’s proposed assignment, upon Developer’s and assignee’s execution of the Assignment and Assumption Agreement, Developer shall be released from any further liability or obligation hereunder related to the portion of the Property and the assignee shall be deemed to be the “Developer,” with all rights and obligations related thereto. The City will review any submittals under this Section within fifteen (15) business days. In the event the City does not respond timely and such submittal clearly identifies this section and the deadline for review, the submittal will be deemed approved. Developer acknowledges that satisfying the terms of this Agreement will achieve certain goals, objectives and public benefits for City which provide material consideration and incentive for City agreeing to enter into this Agreement and agreeing to grant the Existing Approvals, and justify certain restrictions on the right of Developer to assign or transfer its interest under this Agreement in order to assure achievement of such goals, objectives, and public benefits, and therefore Developer agrees to and accepts the restrictions set forth in this Section 10.1 as reasonable and as a material inducement for City to enter into this Agreement. Developer shall pay the reasonable costs borne by City in connection with its review of the proposed assignment, including costs of attorney review and City staff time.

Notwithstanding any other provision of this Agreement to the contrary, each of following transfers are permitted and shall not require City consent under this Section 10.1 (each a “Developer Permitted Transfer”):
(a) Any transfer for financing purposes to secure the funds necessary for construction and/or permanent financing of the Project; (b) An assignment of this Agreement to an Affiliate of Developer; (c) Dedications and grants of easements and rights of way required in accordance with the Project Approvals; or
(d) Any leasing activity.

7.f
October 23, 2023 Packet Pg. 135
33 ARTICLE 11
DEFAULT; REMEDIES; TERMINATION

11.1 Breach and Default. Subject to extensions of time under Section 2.2.2 or by mutual consent in writing, failure by a Party to perform any action or covenant or satisfy any obligation required by this Agreement within thirty (30) days following receipt of written notice from another Party specifying the failure shall constitute a “Default” under this Agreement; provided, however, that if the failure to perform is non-monetary and cannot reasonably be cured within such thirty (30) day period, a Party shall be allowed additional time as is reasonably necessary to cure the failure so long as such Party commences to cure the failure within the thirty (30) day period and thereafter diligently and continuously prosecutes the cure to completion at the earliest practicable date. Notwithstanding the above notice and cure provisions, if such failure to perform by Developer or a circumstance regarding the Project in City’s reasonable opinion creates a public health or welfare emergency, City may but is not obligated to implement a cure and Developer thereafter shall promptly reimburse City its costs and expenses, including attorney’s fees. The City shall provide Developer with reasonable notice appropriate for the circumstances of its determination of and nature of the emergency. If notice cannot be given prior to commencement of the cure, the City shall provide the Developer with its explanation of the emergency and a reasonable explanation for why prior notice could not be given.

11.2 Withholding of Permits. In the event of a Default by Developer, or following notice of breach to Developer pursuant to Section 11.1 above and during the cure period provided therein, upon a finding by the City Manager or his or her designee that Developer is in breach, City shall have the right to refuse to issue any permit or other Additional Project Approvals to which Developer would otherwise have been entitled pursuant to this Agreement until such Default or breach is cured. This provision is in addition to and shall not limit any actions that City may take to enforce the conditions of the Project Approvals.

11.3 Termination. In the event of a Default by a Party, the non-defaulting Party or Parties shall have the right to terminate this Agreement effective immediately upon the defaulting Party’s receipt of the notice of intent to terminate. Termination of this Agreement shall be subject to the provisions of Section 11.8 hereof. The City Clerk shall record a notice of termination of this Agreement with the County Recorder following termination of this Agreement.

11.4 Specific Performance for Violation of a Condition. If City issues a Project Approval pursuant to this Agreement in reliance upon a specified condition being satisfied by Developer in the future, and if Developer then fails to satisfy such condition, City shall be entitled to specific performance for the purpose of causing Developer to satisfy such condition.

11.5 Resolution of Disputes.

11.5.1 Resolution Prior to Legal Action. With regard to any dispute involving the Project or this Agreement, the resolution of which is not provided for by this Agreement or

7.f
October 23, 2023 Packet Pg. 136
34 Applicable Laws, prior to instituting legal action pursuant to Section 11.5.2, a Party shall, at the request of the other Party, meet with designated representatives of the requesting Party promptly following its request, which meeting may be continued by mutual consent. The parties to any such meetings shall attempt in good faith to resolve any such disputes, and by mutual consent may arrange a third party to mediate the dispute. In the event the Parties are not able to resolve the dispute and reach an agreement within fourteen (14) days of the request, either Party may initiate legal action or take such other actions available under this Agreement or the law. Nothing in this Section 11.5.1 shall in any way be interpreted as requiring that Developer and City and/or City’s designee reach agreement with regard to those matters being addressed, nor shall the outcome of these meetings be binding in any way on City or Developer unless expressly agreed to in writing by the parties to such meetings, and the fact of participation in such meetings and any information provided or oral or written statements made by a Party shall not be admissible or otherwise used against the Party in any subsequent legal action. Nothing in this Section 11.8 shall require a Party to postpone instituting any injunctive proceeding or to pursue resolution under this Section 11.5.1 if it believes in good faith that such postponement will cause irreparable harm to such Party.

11.5.2 Institution of Legal Actions. In addition to any other rights or remedies, a Party may institute legal action to cure, correct or remedy any Default, to enforce any covenants or agreements herein, to enjoin any threatened or attempted violation thereof, or to obtain any other remedies consistent with the purpose of this Agreement. Any such legal action shall be brought in the Superior Court for San Mateo County, California, except for actions that include claims in which the Federal District Court for the Northern District of the State of California has original jurisdiction, in which case the Northern District of the State of California shall be the proper venue.

11.5.3 Acceptance of Service of Process. In the event that any legal action is commenced by Developer against City, service of process on City shall be made by personal service upon the City Clerk of City or in such other manner as may be provided by law. In the event that any legal action is commenced by City against Developer, service of process on Developer shall be made by personal service upon Lisa Sobrato Sonsini, Developer’s registered agent for service of process in California, at 599 Castro St. Suite 400, Mountain View, CA 94041, or in such other manner as may be provided by law.

11.6 Rights and Remedies Are Cumulative. The rights and remedies of the Parties are cumulative, and the exercise by a Party of one or more of such rights or remedies shall not preclude the exercise by it, at the same or different times, of any other rights or remedies for the same default or any other default by another Party, except as otherwise expressly provided herein.

11.7 Limitation on Damages. Notwithstanding anything to the contrary herein, neither Party shall have the right to recover any consequential, special, or punitive damages in the event of a Default by the other Party. In no event shall City or the Indemnified Parties be liable

7.f
October 23, 2023 Packet Pg. 137
35 in damages for any default under this Agreement, it being expressly understood and agreed that the sole legal remedy available Developer for a Default by City shall be an action in mandamus, specific performance or other injunctive or declaratory relief to enforce the provisions of this Agreement, or to terminate this Agreement. City shall have all remedies available in law or equity, including but not limited to an action in mandamus, specific performance or other injunctive or declaratory relief to enforce the provisions of this Agreement, or to terminate this Agreement. In addition, City shall have the right to seek actual damages from Developer, including but not limited to enforcing payment of money or the performance of obligations requiring payment of money by Developer under the terms of this Agreement, including but not limited to Sections 5.2, 6.4, 9.6.2, 9.6.3, 10.1,

11.1 and 12.12. As part of recovering such damages, City shall be entitled to interest thereon at the lesser of ten percent (10%) per annum or the maximum rate permitted by law, compounded annually, from the date of expenditure. In connection with the foregoing provisions, each Party acknowledges, warrants and represents that it has been fully informed with respect to, and represented by counsel of such Party’s choice in connection with, the rights and remedies of such Party hereunder and the waivers herein contained, and after such advice and consultation has presently and actually intended, with full knowledge of such Party’s rights and remedies otherwise available at law or in equity, to waive and relinquish such rights and remedies to the extent specified herein, and to rely to the extent herein specified solely on the remedies provided for herein with respect to any breach of this Agreement by another Party.

11.8 Surviving Provisions. In the event this Agreement is terminated, no Party shall have any further rights or obligations hereunder, except for those obligations of Developer which by their terms survive expiration or termination, or which are set forth in Section 9.6 (Cooperation in the Event of Legal Challenge).

ARTICLE 12

MISCELLANEOUS PROVISIONS

12.1 Incorporation of Recitals, Exhibits and Introductory Paragraph. The Recitals contained in this Agreement, the introductory paragraph preceding the Recitals and the Exhibits attached hereto are hereby incorporated into this Agreement as if fully set forth herein.

12.2 Severability. If any term or provision of this Agreement, or the application of any term or provision of this Agreement to a particular situation, is held by a court of competent jurisdiction to be invalid, void or unenforceable, the remaining terms and provisions of this Agreement, or the application of this Agreement to other situations, shall continue in full force and effect unless amended or modified by mutual consent of the Parties

12.3 Construction. Each reference herein to this Agreement or any of the Project Approvals or Additional Project Approvals shall be deemed to refer to the Agreement, Project Approval or Additional Project Approval as it may be amended from time to time, whether or not the particular reference refers to such possible amendment. Section headings in this Agreement are for convenience only and are not intended to be used in interpreting or construing the terms, covenants or conditions of this Agreement. This Agreement has been reviewed and

7.f
October 23, 2023 Packet Pg. 138
36 revised by legal counsel for City and Developer, and no presumption or rule that ambiguities shall be construed against the drafting party shall apply to the interpretation or enforcement of this Agreement. Unless the context clearly requires otherwise, (i) the plural and singular numbers shall each be deemed to include the other; (ii) the masculine, feminine, and neuter genders shall each be deemed to include the others; (iii) “shall,” “will,” or “agrees” are mandatory, and “may” is permissive; (iv) “or” is not exclusive; and (v) “include,” “includes” and “including” are not limiting and shall be construed as if followed by the words “without limitation.”

12.4 Covenants Running with the Land. Except as otherwise more specifically provided in this Agreement, this Agreement and all of its provisions, rights, powers, standards, terms, covenants and obligations, shall be binding upon the Parties and their respective successors (by merger, consolidation, or otherwise) and assigns, and all other persons or entities acquiring the Property, or any interest therein, and shall inure to the benefit of the Parties and their respective successors and assigns, as provided in Government Code Section 65868.5.

12.5 Notices. Any notice or communication required hereunder between City and Developer must be in writing, and may be given either personally, by registered or certified mail (return receipt requested), or by Federal Express or other similar courier promising overnight delivery. If personally delivered, a notice shall be deemed to have been given when delivered to the party to whom it is addressed. If given by registered or certified mail, such notice or communication shall be deemed to have been given and received on the first to occur of (i) actual receipt by any of the addressees designated below as the party to whom notices are to be sent, or (ii) five (5) days after a registered or certified letter containing such notice, properly addressed, with postage prepaid, is deposited in the United States mail. If given by Federal Express or similar courier, a notice or communication shall be deemed to have been given and received on the date delivered as shown on a receipt issued by the courier. Notices and communications may be sent by email to expedite transmittal of information and responses, but shall not be deemed given unless and until followed by transmittal by one of the other processes described in this Section 12.5. Any party hereto may at any time, by giving ten (10) days written notice to the other party hereto, designate any other address in substitution of the address to which such notice or communication shall be given. Such notices or communications shall be given to the parties at their addresses set forth below:

To City: City of San Carlos
600 Elm Street
San Carlos, CA 94070
Attention: Director of Community Development
With a copy to: City of San Carlos
600 Elm Street
San Carlos, CA 94070
Attention: City Attorney

7.f
October 23, 2023 Packet Pg. 139
37 To Developer: The Sobrato Family Foundation
c/o The Sobrato Organization
599 Castro St. Suite 400
Mountain View, CA 94041
Attention: Lisa Sobrato Sonsini
With a copy to: The Sobrato Organization
599 Castro St. Suite 400
Mountain View, CA 94041
Attention: Robert Tersini
Attention: Jeff Sobrato
Holland & Knight
560 Mission Street, Suite 1900
San Francisco, CA 94105
Attention: Tamsen Plume

12.6 Counterparts and Exhibits; Entire Agreement. This Agreement may be executed in multiple counterparts, each of which shall be deemed to be an original. This Agreement, together with the Existing Approvals and attached Exhibits, constitutes the final and exclusive understanding and agreement of the Parties and supersedes all negotiations or previous agreements of the Parties with respect to all or any part of the subject matter hereof.

12.7 Recordation of Agreement. Pursuant to California Government Code Section 65868.5, the City Clerk will record this Agreement no later than ten (10) days after the Effective Date.

12.8 No Joint Venture or Partnership. It is specifically understood and agreed to by and between the Parties hereto that: (i) the Project is a private development; (ii) City has no interest or responsibilities for, or duty to, third parties concerning any public improvements until such time, and only until such time, that City accepts the same pursuant to the provisions of this Agreement or in connection with the various Project Approvals or Additional Project Approvals; (iii) Developer shall have full power over and exclusive control of the Project herein described, subject only to the limitations and obligations of Developer under this Agreement, Project Approvals, Additional Project Approvals, and Applicable Laws; and (iv) City and Developer hereby renounce the existence of any form of agency relationship, joint venture or partnership between City and Developer and agree that nothing contained herein or in any document executed in connection herewith shall be construed as creating any such relationship between City and Developer.

12.9 Waivers. Notwithstanding any other provision in this Agreement, any failures or delays by any Party in asserting any of its rights and remedies under this Agreement shall not operate as a waiver of any such rights or remedies, or deprive any such Party of its right to institute and maintain any actions or proceedings which it may deem necessary to protect, assert or enforce any such rights or remedies. A Party may specifically and expressly waive in writing any condition or breach of this Agreement by another Party, but no such waiver shall constitute a further or continuing waiver of any preceding or succeeding breach of the same or any other provision. Consent by one Party to any act by another Party shall not be

7.f
October 23, 2023 Packet Pg. 140
38 deemed to imply consent or waiver of the necessity of obtaining such consent for the same or similar acts in the future.

12.10 California Law; Venue. This Agreement shall be construed and enforced in accordance with the laws of the State of California, without reference to choice of law provisions. The exclusive venue for any disputes or legal actions shall be the Superior Court of California in and for the County of San Mateo or the US District Court, Northern California District.

12.11 City Approvals and Actions. Whenever reference is made herein to an action or approval to be undertaken by City, the City Manager or his or her designee is authorized to act on behalf of City, unless specifically provided otherwise or the context requires otherwise.

12.12 Estoppel Certificates. A Party may, at any time during the Term of this Agreement, and from time to time, deliver written notice to another Party requesting such Party to certify in writing that, to the knowledge of the certifying Party, (i) this Agreement is in full force and effect and a binding obligation of the Parties, (ii) this Agreement has not been amended or modified either orally or in writing, or if amended; identifying the amendments, (iii) the requesting Party is not in default in the performance of its obligations under this Agreement, or if in default, to describe therein the nature and amount of any such defaults, and (iv) any other information reasonably requested that relates to implementation of the Agreement. The requesting Party shall be responsible for all reasonable costs incurred by the Party from which such certification is requested and shall reimburse such costs within thirty (30) days of receiving the certifying Party’s request for reimbursement. The Party receiving a request hereunder shall execute and return such certificate or give a written, detailed response explaining why it will not do so within fourteen (14) days following the receipt thereof. The failure of either Party to provide the requested certificate within such fourteen (14) day period shall constitute a confirmation that this Agreement is in full force and effect and no modification or default exists. The Director of Community Development, the Planning Director or the City Manager, or their authorized designee, shall have the right to execute any certificate requested by Developer hereunder. City acknowledges that a certificate hereunder may be relied upon by transferees and Mortgagees.

12.13 No Third Party Beneficiaries. City and Developer hereby renounce the existence of any third party beneficiary to this Agreement and agree that nothing contained herein shall be construed as giving any other person or entity third party beneficiary status.

12.14 Signatures. The individuals executing this Agreement represent and warrant that they have the right, power, legal capacity, and authority to enter into and to execute this Agreement on behalf of the respective legal entities of Developer and City.

12.15 Time. Time is of the essence of this Agreement and of each and every term and condition hereof.

12.16 Days. The word “days” as used in this Agreement refers to calendar days unless specifically provided otherwise. In the event that any period to perform an obligation or notice period under this Agreement starts or ends on a Saturday, Sunday, or state or national holiday, the applicable time period shall be extended to the next regular City business day.

7.f
October 23, 2023 Packet Pg. 141
39 IN WITNESS WHEREOF, this Agreement has been entered into by and between Developer and City as of the day and year first above written.

CITY:

City of San Carlos,
a municipal corporation organized and existing
under the laws of the State of California
By:

Name:

Title:
[signature must be notarized]
APPROVED AS TO FORM:

By:

Name:

Title:

ATTEST:

By:

Name:

Title:
[Developer signatures begin on next page.]

7.f
October 23, 2023 Packet Pg. 142
40 DEVELOPER:

THE SOBRATO FAMILY FOUNDATION,
a California nonprofit public benefit corporation
By:

Name: Lisa Sobrato Sonsini
Title: Secretary
[signature must be notarized]

7.f
October 23, 2023 Packet Pg. 143
41 State of ) County of )
On , before me, , a notary public,
personally appeared , who proved to me on the basis of satisfactory evidence to be the person(s) whose name(s) is/are subscribed to the within instrument and acknowledged to me that he/she/they executed the same in his/her/their authorized capacity(ies), and that by his/her/their signature(s) on the instrument the person(s), or the entity upon behalf of which the person(s) acted, executed the instrument.

I certify under PENALTY OF PERJURY under the laws of the State of California that the foregoing paragraph is true and correct.

WITNESS my hand and official seal.

Signature (Seal)
A notary public or other officer completing this certificate verifies only the identity of the individual who signed the document to which this certificate is attached, and not the truthfulness, accuracy, or validity of that document.

7.f
October 23, 2023 Packet Pg. 144
42 State of ) County of )
On , before me, , a notary public,
personally appeared , who proved to me on the basis of satisfactory evidence to be the person(s) whose name(s) is/are subscribed to the within instrument and acknowledged to me that he/she/they executed the same in his/her/their authorized capacity(ies), and that by his/her/their signature(s) on the instrument the person(s), or the entity upon behalf of which the person(s) acted, executed the instrument.

I certify under PENALTY OF PERJURY under the laws of the State of California that the foregoing paragraph is true and correct.

WITNESS my hand and official seal.

Signature (Seal)
A notary public or other officer completing this certificate verifies only the identity of the individual who signed the document to which this certificate is attached, and not the truthfulness, accuracy, or validity of that document.

7.f
October 23, 2023 Packet Pg. 145
43 Exhibit A
Property Legal Description

7.f
October 23, 2023 Packet Pg. 146
Order Number: NCS-1033730-SC
Page Number: 9
First American Title Insurance Company

LEGAL DESCRIPTION
Real property in the City of San Carlos, County of San Mateo, State of California, described as follows:

PARCEL ONE:

BEGINNING AT A POINT ON THE NORTHEASTERLY LINE OF THE COUNTY ROAD LEADING FROM SAN CARLOS TO REDWOOD CITY, DISTANT THEREON SOUTH 42° 22' 30" EAST 706.74 FEET FROM THE

MOST WESTERLY CORNER OF THAT TRACT OF LAND KNOWN AS SPEEDWAY ACRES CONVEYED TO ASA E. HULL FROM C. S. MORTON, ET AL., BY DEED DATED JUNE 16, 1924 AND RECORDED IN BOOK 128 AT PAGE 107 (23249A), OFFICIAL RECORDS OF SAN MATEO COUNTY THENCE ALONG THE NORTHEASTERLY LINE OF SAID COUNTY ROAD, SOUTH 42° 22' 30" EAST 206.41 FEET THENCE LEAVING THE LAST MENTIONED LINE, NORTH 48° 53' EAST 234.56 FEET TO THE SOUTHWESTERLY LINE OF THE LAND DESCRIBED AS PARCEL 2 IN THE DEED TO SOUTHERN PACIFIC RAILROAD COMPANY RECORDED JUNE 18, 1926 IN BOOK 243 AT PAGE 17 (62690A), OFFICIAL RECORDS OF SAN MATEO COUNTY THENCE ALONG THE LAST MENTIONED LINE, NORTH 42° 22' 30" WEST 206.41 FEET TO A POINT WHICH BEARS NORTH 48° 53' EAST FROM THE POINT OF BEGINNING; THENCE SOUTH 48° 53' WEST 234.56 FEET TO THE POINT OF BEGINNING.

PARCEL TWO:

BEGINNING AT A POINT ON THE NORTHEASTERLY LINE OF THE COUNTY ROAD LEADING FROM SAN CARLOS TO REDWOOD CITY, DISTANT THEREON SOUTH 42° 22' 30" EAST 913.16 FEET FROM THE

MOST WESTERLY CORNER OF THAT TRACT OF LAND KNOWN AS SPEEDWAY ACRES CONVEYED TO ASA E. HULL FROM C. B. MORTON, ET AL., BY DEED DATED JUNE 16, 1924 AND RECORDED IN BOOK 128 AT PAGE 107 (23249A), OFFICIAL RECORDS OF SAN MATEO COUNTY; THENCE FROM SAID POINT OF BEGINNING LEAVING THE NORTHEASTERLY LINE OF SAID COUNTY ROAD, NORTH 48° 43' EAST 234.56 FEET TO THE SOUTHWESTERLY LINE OF THE LAND DESCRIBED AS PARCEL 2 IN THE DEED TO SOUTHERN PACIFIC RAILROAD COMPANY RECORDED JUNE 18, 1926 IN BOOK 243 AT PAGE 17 (62690A), OFFICIAL RECORDS OF SAN MATEO COUNTY THENCE ALONG THE LAST MENTIONED LINE, SOUTH 42° 22' 30" EAST 56.68 FEET TO THE NORTHWESTERLY LINE OF COMMERCIAL WAY AS

ESTABLISHED BY DEED TO THE CITY OF SAN CARLOS, A MUNICIPAL CORPORATION, RECORDED OCTOBER 12, 1973 IN BOOK 6485 AT PAGE 501 (82827AG) OFFICIAL RECORDS OF SAN MATEO

COUNTY THENCE ALONG SAID NORTHWESTERLY LINE OF COMMERCIAL WAY AND THE SOUTHWESTERLY PROLONGATION THEREOF, SOUTH 48° 53' WEST 234.56 FEET TO THE

NORTHEASTERLY LINE OF SAID COUNTY ROAD THENCE ALONG THE LAST MENTIONED LINE, NORTH 42° 12' 30" WEST 56.68 FEET TO THE POINT OF BEGINNING.

PARCEL THREE:

BEING ALL OF PARCEL 2 AS DESCRIBED IN THE DEED FROM CALIFORNIA CONCRETE PRODUCTS AND ASA E. HULL TO SOUTHERN PACIFIC RAILROAD COMPANY RECORDED JUNE 18, 1926 IN VOLUME 243 OF OFFICIAL RECORDS AT PAGE 17 (243 O.R. 17); AND A PORTION OF PARCEL 2 AS DESCRIBED IN THE DEED FROM K.A. WINTER ET. AL. TO SOUTHERN PACIFIC RAILROAD COMPANY RECORDED JUNE 18, 1926 IN VOLUME 243 OF OFFICIAL RECORDS AT PAGE 12 (243 O.R. 12); BEING MORE PARTICULARLY DESCRIBED AS FOLLOWS:

BEGINNING AT THE MOST SOUTHERLY CORNER OF SAID PARCEL 2 OF SAID 243 O.R. 17; THENCE ALONG THE SOUTHWESTERLY LINE OF SAID PARCEL NORTH 42°22'30" WEST 293.10 FEET TO THE MOST SOUTHERLY CORNER OF SAID PARCEL 2 OF SAID 243 O.R. 12; THENCE ALONG THE SOUTHWESTERLY LINE OF SAID PARCEL NORTH 42°22'30" WEST 56.70 FEET TO

7.f
October 23, 2023 Packet Pg. 147
Order Number: NCS-1033730-SC
Page Number: 10
First American Title Insurance Company
THE BEGINNING OF A TANGENT CURVE TO THE LEFT HAVING A RADIUS OF 397.97 FEET; THENCE NORTHWESTERLY ALONG SAID CURVE THROUGH A CENTRAL ANGLE OF 1°29'08" A DISTANCE OF 10.32 FEET TO THE SOUTHEASTERLY LINE OF THE LANDS AS DESCRIBED IN THE QUITCLAIM DEED FROM UNION PACIFIC RAILROAD COMPANY TO KELLOGG ET. AL. RECORDED MAY 31, 2002 IN DOCUMENT NUMBER 2002-106037, OFFICIAL RECORDS OF SAN MATEO COUNTY; THENCE ALONG SAID SOUTHEASTERLY LINE NORTH 48°53'00" EAST 17.01 FEET TO A POINT ON THE NORTHEASTERLY LINE OF SAID PARCEL 2 OF SAID 243 O.R. 12; SAID POINT LYING A CURVE CONCAVE TO THE SOUTHWEST HAVING A RADIUS OF 414.97 FEET; A RADIAL LINE TO SAID POINT BEARING NORTH 46°15'05" EAST;
THENCE SOUTHEASTERLY ALONG SAID CURVE THROUGH A CENTRAL ANGLE OF 1°22'25" A DISTANCE OF 9.95 FEET;
THENCE TANGENT FROM SAID CURVE ALONG SAID NORTHEASTERLY LINE SOUTH 42°22'30" EAST

57.07 FEET TO THE MOST NORTHERLY CORNER OF SAID PARCEL 2 OF SAID 243 O.R. 17; THENCE ALONG THE NORTHEASTERLY LINE OF SAID PARCEL SOUTH 42°22'30" EAST 293.10 FEET TO THE SOUTHEASTERLY CORNER OF SAID PARCEL;
THENCE ALONG THE SOUTHEASTERLY LINE OF SAID PARCEL SOUTH 48°53'00" WEST 17.00 FEET TO THE POINT OF BEGINNING.

EXCEPTING THEREFROM ALL MINERALS AND ALL MINERAL RIGHTS OF EVERY KIND AND CHARACTER

NOW KNOWN TO EXIST OR HEREAFTER DISCOVERED UNDERLYING THE PROPERTY, INCLUDING,

WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, OIL AND GAS AND RIGHTS THERETO,

TOGETHER WITH THE SOLE, EXCLUSIVE AND PERPETUAL RIGHT TO EXPLORE FOR, REMOVE AND

DISPOSE OF SAID MINERALS BY ANY MEANS OR METHODS SUITABLE TO GRANTOR, ITS SUCCESSORS

AND ASSIGNS, BUT WITHOUT ENTERING UPON OR USING THE SURFACE OF THE PROPERTY, AND IN

SUCH MANNER AS NOT TO DAMAGE THE SURFACE OF THE PROPERTY, OR TO INTERFERE WITH THE

USE THEREOF BY GRANTEE, HER HEIRS AND ASSIGNS, AS RESERVED IN QUITCLAIM DEED RECORDED OCTOBER 26, 2007 AS INSTRUMENT NO. 2007-154663 OF OFFICIAL RECORDS.

PARCEL FOUR:

BEGINNING AT THE MOST SOUTHERLY CORNER OF THAT CERTAIN 20 ACRE TRACT DESCRIBED IN THE AGREEMENT BETWEEN ASA B. HULL AND I.H. WINTER ET AL, RECORDED NOVEMBER 24, 1925 IN BOOK 201 OF OFFICIAL RECORDS OF SAN MATEO COUNTY AT PAGE 290; THENCE FROM SAID POINT OF BEGINNING ALONG THE SOUTHEASTERLY LINE OF SAID 20 ACRE TRACT, NORTH 48°53' EAST 230.00 FEET; THENCE LEAVING SAID SOUTHEASTERLY LINE AND RUNNING ACROSS SAID 20 ACRE TRACT, NORTH 42° 22' 30" WEST 90.02 FEET AND SOUTH 48° 53' WEST 230.00 FEET TO A POINT ON THE NORTHEASTERLY LINE OF THE COUNTY ROAD LEADING FROM REDWOOD CITY TO CARLOS; THENCE ALONG SAID NORTHEASTERLY LINE OF SAID COUNTY ROAD, SOUTH 42° 22' 30" EAST 90.03 FEET TO THE POINT OF BEGINNING.

PARCEL FIVE:

BEGINNING AT A POINT ON THE NORTHEASTERLY LINE OF THAT CERTAIN COUNTY ROAD LEADING

FROM REDWOOD CITY TO SAN CARLOS, SAID POINT OF BEGINNING BEING DISTANT ALONG SAID NORTHEASTERLY LINE OF SAID COUNTY ROAD NORTH 42° 22’ 30” WEST 180.04 FEET FROM THE MOST SOUTHERLY CORNER OF THAT CERTAIN 20 ACRE TRACT DESCRIBED IN AGREEMENT BETWEEN ASA E. HULL AND K.A. WINTER, ET AL, SAID AGREEMENT BEING FILED FOR RECORD NOVEMBER 24, 1925 IN VOLUME 201 OF OFFICIAL RECORDS AT PAGE 290, RECORDS OF SAN MATEO COUNTY, CALIFORNIA; THENCE FROM SAID POINT OF BEGINNING ALONG SAID NORTHEASTERLY LINE OF SAID

7.f
October 23, 2023 Packet Pg. 148
Order Number: NCS-1033730-SC
Page Number: 11
First American Title Insurance Company
COUNTY ROAD NORTH 42° 22’ 30” WEST 90.02 FEET TO A POINT WHERE SAID NORTHEASTERLY LINE OF SAID COUNTY ROAD IS INTERSECTED BY THE SOUTHEASTERLY LINE OF A 50 FOOT PRIVATE ROAD RUNNING THROUGH ABOVE DESCRIBED 20 ACRE TRACT; THENCE ALONG SAID SOUTHEASTERLY LINE OF SAID 50 FOOT ROAD NORTH 48° 53’ EAST 230 FEET; THENCE LEAVING SAID SOUTHEASTERLY LINE OF SAID 50 FOOT PRIVATE ROAD AND RUNNING SOUTH 42° 22’ 30” EAST 90.02 FEET AND SOUTH 48° 53’ WEST 230.0 FEET TO THE POINT OF BEGINNING.

PARCEL SIX:

BEGINNING AT A POINT ON THE NORTHEASTERLY LINE OF THE OLD COUNTY ROAD FROM REDWOOD

CITY TO SAN CARLOS (SAID ROAD LYING NORTHEASTERLY OF THE TRACKS OF THE SOUTHERN

PACIFIC RAILROAD), SAID POINT OF BEGINNING BEING DISTANT ALONG SAID NORTHEASTERLY LINE OF SAID ROAD, NORTH 42° 22’ 30” WEST 90.02 FEET FROM THE MOST SOUTHERLY CORNER OF THAT CERTAIN 20 ACRE TRACT DESCRIBED IN AGREEMENT BETWEEN ASA E. HULL AND K.A. WINTER, ET AL, RECORDED NOVEMBER 24, 1925 IN VOLUME 201 OF OFFICIAL RECORDS AT PAGE 290, RECORDS OF SAN MATEO COUNTY, CALIFORNIA; THENCE FROM SAID POINT OF BEGINNING ALONG SAID NORTHEASTERLY LINE OF SAID COUNTY ROAD, NORTH 42°22’ 30” WEST 90.02 FEET; THENCE NORTH 48° 53’ EAST 230.0 FEET; THENCE SOUTH 42°22’ 30” EAST 90.02 FEET; THENCE SOUTH 48°53’ WEST 230.0 FEET TO THE POINT OF BEGINNING.

PARCEL SEVEN:

A PARCEL OF LAND SITUATE IN THE CITY OF SAN CARLOS, COUNTY OF SAN MATEO, STATE OF CALIFORNIA, BEING PARCEL THREE AS DESCRIBED IN A DEED RECORDED NOVEMBER 26, 1991 IN DOCUMENT NUMBER 91155625 OFFICIAL RECORDS OF SAN MATEO COUNTY, MORE PARTICULARLY DESCRIBED AS FOLLOWS:

BEGINNING AT A POINT ON THE SOUTHEASTERLY LINE OF THAT CERTAIN 20 ACRES TRACT DESCRIBED IN THE AGREEMENT BETWEEN ASA E. HULL AND K.A. WINTER, ET AL, RECORDED NOVEMBER 24, 1925 IN BOOK 201 OFFICIAL RECORDS OF SAN MATEO COUNTY, PAGE 290, SAID POINT OF BEGINNING BEING DISTANT ALONG SAID SOUTHEASTERLY LINE NORTH 48° 53’ EAST 230.0 FEET FROM THE MOST SOUTHERLY CORNER OF SAID 20 ACRE TRACT; THENCE FROM SAID POINT OF BEGINNING ALONG SAID SOUTHEASTERLY LINE NORTH 48° 53’ EAST, 100.00 FEET, THENCE LEAVING SAID SOUTHEASTERLY LINE AND RUNNING ACROSS SAID 20 ACRE TRACT NORTH 41° 07’ WEST, 270.00 FEET OF THE SOUTHEASTERLY LINE OF A 50 FOOT PRIVATE ROAD RUNNING THROUGH THE ABOVE DESCRIBED 20 ACRE TRACT; THENCE ALONG SAID SOUTHEASTERLY LINE OF SAID 50 FOOT PRIVATE ROAD SOUTH 48° 53’ WEST, 105.93 FEET; THENCE LEAVING SAID SOUTHEASTERLY LINE OF SAID 50 FOOT ROAD SOUTH 42° 22’ 30” EAST, 270.06 FEET TO THE POINT OF BEGINNING.

EXCEPTING THEREFROM THAT PORTION OF THE ABOVE DESCRIBED PROPERTY WHICH LIES SOUTHEASTERLY OF A LINE PARALLEL TO AND 90.02 FEET MEASURED PERPENDICULARLY NORTHWESTERLY OF THE ABOVE SAID SOUTHEASTERLY LINE OF SAID 20 ACRE TRACT AND NORTHEASTERLY OF THE COURSE CALLED SOUTH 42° 22’ 30” EAST, 57.074 FEET AND THE NORTHWESTERLY EXTENSION THEREOF, AS SAID COURSE IS DESCRIBED IN PARCEL #2 OF THE ABOVE SAID DEED RECORDED JUNE 18, 1926 IN BOOK 243 OFFICIAL RECORDS OF SAN MATEO COUNTY PAGE 12.

ALSO EXCEPTING THEREFROM, THAT PORTION THEREOF LYING WITHIN THE PARCEL DESCRIBED IN

THE QUITCLAIM DEED FROM UNION PACIFIC RAILROAD COMPANY, A DELAWARE CORPORATION TO WANDA MAE ADAMS RECORDED OCTOBER 26, 2007 AS INSTRUMENT NO. 2007-154663 OF OFFICIAL RECORDS.

For reference purposes only:

7.f
October 23, 2023 Packet Pg. 149
Order Number: NCS-1033730-SC
Page Number: 12
First American Title Insurance Company
APN: 046-182-100 (affects Parcel One);
046-182-110 (affects Parcel Two);
046-182-150 (affects Parcel Three);
046-135-030 (affects Parcel Four);
046-135-010 (affects Parcel Five);
046-135-020 (affects Parcel Six);
046-135-040 (affects portion of Parcel Seven);
046-134-050 (affects portion of Parcel Seven);
046-134-060 (affects portion of Parcel Seven);
and 046-133-160 (affects portion of Parcel Seven)
JPN:
046-018-182-04A
046-018-182-05A
046-013-135-03A
046-013-135-01A
046-013-135-02A
046-013-134-03A
046-013-133-016A

7.f
October 23, 2023 Packet Pg. 150
44 Exhibit B
Impact Fees
Commercial Linkage fee
(Chapter 8.51 of the San Carlos Municipal Code)
$6,634,785.00
Sewer fees (connection and capacity)
(Chapter 13.04 of the San Carlos Municipal Code)
$2,893,081.89
Traffic impact fee
(Chapter 8.50 of the San Carlos Municipal Code)
$1,829,614.58
Child Care impact fee
(Chapter 8.52 of the San Carlos Municipal Code)
$1,621,543.00
Total City impact fees $12,979,024.47

7.f
October 23, 2023 Packet Pg. 151
45 Exhibit C
Initial Shell Condition
Exhibit | Landlord Work | Initial Shell Condition
Approx. SF: 1,500 The Exhibit describes the Premises Delivery obligations of the landlord.

SCOPE CATEGORY Details
Flooring
Floor Type “AS-IS” Post tensioned concrete slab
Doors & Windows
Storefront Windows &
Doors
- One pair of storefront doors
- Any modifications to base building storefront require Landlord’s approval and are Tenant’s responsibility.
- Rekeying of locks is the responsibility of Tenant.

Finishes
Demising Wall
- Demising walls consisting of 6" metal or wood studs, batt insulation and 5/8" Type X
- Drywall from floor to deck.

Perimeter Walls &
Roof
- Insulation to be installed on the interior side of all perimeter walls from floor to deck
Fire Suppression
Fire/Life Safety
- Fire suppression, life safety systems and fire protection equipment as required by local fire department code for the shelf space.
- Tenant is required to modify systems lo accommodate its design and as required per local jurisdictional requirements.

Plumbing
Water Distribution
- One (1) 1" domestic cold-water supply line with shut off valve stubbed into the space.

Tenant is responsible for all connections, equipment and devices as required by Tenant design or local jurisdiction requirements.

Sanitary Sewer
- One (1) 4' sanitary sewer line to service the space.

Tenant is responsible for all connections, equipment and devices as required by Tenant design or local jurisdiction codes.

7.f
October 23, 2023 Packet Pg. 152
46 HVAC
HVAC
- HVAC duct chase distribution into space based on standard retail use. All distribution within space by tenant. Any extraordinary requirements necessitated because of Tenant’s use of the Premises will be at the expense of Tenant. Roof top space provided for tenant’s equipment
Electrical Signs
- One (1) J-box for signage located at the main entrance lo space.

Tenant is responsible for all connections, equipment and devices as required by Tenant design or local jurisdiction codes, including exit signs.

Medium-Voltage
Electrical Distribution
- Electrical service provided at main electrical room to be 400 Amps (120/208V, 3-phase, 4-wire) Distribution to space by tenant
- Lighting and exit signs for the space including new restroom that meet the local jurisdiction codes.

Communications
Tenant will be required upon the “Delivery of the Premises” to switch all utility account(s) responsibility and all billing information into their name.

Telephone System
- 2” telephone/data conduit to space with pull string.
- Tenant is responsible for all connections, equipment and devices as required by Tenant design or local jurisdiction codes and for provisioning telephone and data service.

Water Utility
- Landlord to provide the water submeter (including capacity charges) with a 5/8" restricted submeter size. Any upsizing of the submeter is the responsibility of the Tenant (in no event shall exceed a 1” submeter) and shall be reimbursed to the Landlord.
- Tenant is responsible for activation of the water submeter account with the local utility.
- Tenant is responsible for all plumbing distribution and equipment.

Electric Meter
- LL provided meter socket.
- Tenant is responsible for activation their account in their name with the local utility company.

Notation:
- Tenant is responsible for all electrical distribution and equipment.

All work other than that set forth above will be at Tenant’s expense and subject to Landlord's written prior approval.

Landlord will neither supply nor install: specially ceilings,

7.f
October 23, 2023 Packet Pg. 153
47 restrooms. trade fixtures; additional lighting fixtures and built-in lighting; special finishes; acoustic treatment; plastering; signs: locker. show window floors and backs; curtain walls and interior partitions (except as set forth above); special ceilings; restrooms or special toilet rooms; electrical, plumbing and ventilation connections to trade fixtures. or required for special uses and trade processes; bulletproof glass. bank vaults, remote tellers, or any such custom installations.

7.f
October 23, 2023 Packet Pg. 154
48 Exhibit D
[Form of] POPA Easement

RECORDING REQUESTED BY
AND WHEN RECORDED RETURN TO:

City of San Carlos
600 Elm Street
San Carlos, California 94070
Attention: City Clerk
Record for the Benefit of
The City of San Carlos
Pursuant to Government Code
Section 27383
Space Above Reserved for Recorder’s Use Only
[FORM OF] PRIVATELY OWNED PUBLICLY ACCESSIBLE OPEN SPACE EASEMENT

AND MAINTENANCE AGREEMENT
This Privately Owned Publicly Accessible Open Space Easement and Maintenance Agreement (“POPA Agreement”) is made and entered into on this ____ day of , (“POPA Agreement Effective Date”) by and between THE SOBRATO FAMILY FOUNDATION, a California nonprofit public benefit corporation (“Owner”), and the CITY OF SAN CARLOS, a charter city and California municipal corporation (“City”) (together, the “Parties”).

R E C I T A L S
A. Owner is the current fee owner of that certain real property consisting of approximately 3.4 acres located within the City of San Carlos, County of San Mateo, State of California, designated as APNs 046-133-160, 046-134-050, 046-134-060, 046-135-010, 046-135- 020, 046-135-030, 046-138-040, 046-182-100, 046-182-110 and 046-182-150 and legally described in Exhibit “A”, attached hereto and incorporated herein by reference (the “Property”).

B. The Property is being developed as a mixed-use and R&D/life sciences development project consisting of approximately 339,170 gross square feet of office, R&D and life sciences uses in two buildings, two levels of below-grade parking and a front plaza and central courtyard (the “Project”).

C. On [_________], the City Council of the City of San Carlos adopted Ordinance No. [_________], approving a Development Agreement by and between City and Owner

7.f
October 23, 2023 Packet Pg. 155
49 (“Development Agreement”) and issued several other approvals identified in the Development Agreement (“Project Approvals”), subject to certain conditions of approval (“Conditions”).

D. The Project Approvals contemplate, among other things, that the Owner will designate, design and improve an approximately 5,000 square foot privately owned publicly accessible (“POPA”) central outdoor plaza (the “Front Plaza”) adjacent to a restaurant/coffee shop or other permitted use (the “Restaurant/Coffee Shop”) within the Property in the area legally described and shown in Exhibit “B.1”, attached hereto and incorporated herein by reference (“Front Plaza Easement Area”).

E. The Project Approvals also contemplate that the Owner will designate, design and improve an approximately 12,000 square foot POPA outdoor courtyard centrally located between the buildings (the “Courtyard”) containing outdoor amenities for the future tenant and the public within the Property in the area legally described and show in Exhibit “B.2”, attached hereto and incorporated herein by reference (“ Courtyard Easement Area”). The Front Plaza Easement Area and Courtyard Easement Area are referred to herein as, collectively, the “Easement Areas.” F. City and Owner now desire that Owner grant to City easements for use and enjoyment of the privately owned Easement Areas as publicly accessible space and provide for the maintenance of the Easement Areas as set forth below.

POPA EASEMENT AGREEMENT
NOW, THEREFORE, the Parties hereby incorporate the above recitals by this reference and agree as follows:

1. Grant of Front Plaza Easement and Courtyard Easement. For valuable consideration, including the benefits and rights conferred upon Owner under the Project Approvals and subject to the terms of this POPA Agreement, Owner hereby grants and dedicates to the City a nonexclusive easement for use and enjoyment by the general public on, over and across that certain real property located in the Front Plaza Easement Area, as described and shown on Exhibit “B.1” (“Front Plaza Easement”) and the Courtyard Easement Area, as described and shown on Exhibit “B.2” (“Courtyard Easement”). These grants of Front Plaza Easement and Courtyard Easement convey no rights affecting the use of Owner’s lands that are not included in the Easement Areas and Owner reserves the right to lands outside the Easement Areas in any lawful manner.

2. Use and Closure. The public’s right to use the Easement Areas is limited to the longer of daylight hours (sunrise to sunset) or, for the Front Plaza Easement, the hours that the Restaurant/Coffee Shop is open to the public. The Easement Areas may be used by the general public for informal recreational uses, which may include lawn areas, pathways, planted areas, benches, tables, chairs, common areas, green space and the like. The Easement Areas shall be open to the public, at minimum, from sunrise to sunset, 7 days a week, except for closures permitted in Section 5.

3. Maintenance. Owner covenants and agrees that it shall maintain, repair and replace, or cause to be maintained, repaired and replaced, the Easement Areas, and all improvements, including lighting, hardscaping and landscaping, located thereon, in first-class condition and repair

7.f
October 23, 2023 Packet Pg. 156
50 and in compliance with the Maintenance Standards (defined below). Owner’s compliance with the Maintenance Standards shall be judged by a comparative standard with the custom and practice generally applicable to comparable first-class passive recreational areas located within San Mateo County. To accomplish such maintenance, Owner shall either staff or contract with and hire licensed and qualified personnel to perform such maintenance work, including the provision of labor, equipment, materials, support facilities, and any and all other items necessary to comply with the requirements of this Section 3. All maintenance work shall conform to all applicable Federal and State Occupational Safety and Health Act standards and regulations for the performance of maintenance. The following standards (“Maintenance Standards”) shall be complied with by Owner and its maintenance staff, contractors and subcontractors:
a. Maintain the surface of all pedestrian areas level, smooth and evenly covered with the type of surfacing material originally installed thereon or such substitute therefor as shall be in all respects equal thereto or better in quality, appearance and durability; b. Remove all papers, debris, filth and refuse, and sweep, wash down and/or clean all hard surfaces, including brick, metal, concrete, glass, wood and other permanent poles, walls or structural members as required;
c. Maintain such appropriate entrance, exit and directional signs, markers and lights as shall be reasonably required;
d. Clean lighting fixtures and re-lamp and/or re-ballast as needed; e. Maintain, repair and replace and keep in first-class condition all benches, outdoor dining furniture, planters, trash containers, and other exterior elements, if any; f. Maintain, repair and replace all drinking fountains and associated plumbing; g. Provide adequate security lighting in all areas, and maintain, repair and replace all security and decorative light fixtures and associated wiring systems; h. Pay the electrical expense of operating the lighting and irrigation controller, upon the direct receipt of invoices for electrical service from Pacific Gas and Electric; i. Maintain, repair and replace all surface and storm lateral drainage systems; j. Promptly remove any graffiti on or about the Easement Areas; k. Perform landscape maintenance including watering/irrigation, fertilization, pruning, trimming, shaping, and replacement, as needed, of all trees, shrubs, grass, and other plants or plant materials, weeding of all plants, planters and other planted areas, staking for support of plants as necessary, and clearance, cleaning and proper disposal of all cuttings, weeds, leaves and other debris; and
l. Perform other maintenance as required by law.

7.f
October 23, 2023 Packet Pg. 157
51 4. Default and Remedies. Breach of, failure, or delay by Owner to perform any term or condition of this POPA Agreement shall constitute a default. In the event of any default of any term, condition, or obligation of this POPA Agreement, City shall give the Owner notice in writing specifying the nature of the alleged default and the manner in which such default may be satisfactorily cured (“Notice of Breach”). The defaulting party shall cure the default within 30 days following receipt of the Notice of Breach, provided, however, if the nature of the alleged default is non-monetary and such that it cannot reasonably be cured within such 30-day period, then the commencement of the cure within such time period, and the diligent prosecution to completion of the cure thereafter, shall be deemed to be a cure, provided that if the cure is not diligently prosecuted to completion, then no additional cure period shall be provided. If the alleged failure is cured within the time provided above, then no default shall exist and the City shall take no further action to exercise any remedies available hereunder. If the alleged failure is not cured, then a default shall exist under this POPA Agreement and the City may bring any action at law or in equity to enforce the terms of this POPA Agreement. In addition, if the default is the failure to meet the Maintenance Standards set forth in Section 3 above, the City, in addition to its other rights and remedies, may enter and perform or cause its agents and contractors to enter the Easement Areas and perform the required maintenance and City costs shall be reimbursed by Owner within thirty (30) days of billing by City or City may record a lien or place the amount owed as a special assessment against the Property in the amount of the work performed.

5. Temporary Closure for Maintenance and Events. Owner reserves the right to temporarily exclude the public from or limit public access to all or portions of the Easement Areas if necessary to address safety concerns and perform maintenance and repairs to improvements within or immediately adjacent to the Front Plaza. In addition, the Owner reserves the right to exclude the public from all or portions of the Easement Areas a reasonable limited number of times per year for events or exclusive use of the Easement Areas by tenants of the Project (each individually a “Tenant Event” and collectively, “Tenant Events”), not to exceed four (4) Tenant Events per year for the Front Plaza Easement Area, and not to exceed two (2) times per month for the Courtyard Easement Area. Each such Tenant Event may not last more than 24 hours (although two Tenant Events could allow a total of 48 hours), including any set up or tear down/clean-up activities. In addition to the Tenant Events, non-profits or other not-for-profit community organizations with principal offices within the City limits (“Community Groups”) may hold private events on the Front Plaza Easement Area and/or Courtyard Easement Area six (6) times per year (each no more than 24 hours per event including set up/clean up) under a typical form of event agreement (i.e. event details, cleaning fee, insurance and liability protection for the Owner, organization and City).

Prior to the opening of the Front Plaza and Courtyard to tenants and the public, Developer shall designate an individual to whom Community Groups may make reservation requests or develop an electronic system for submission of reservation requests. The Developer shall require tenants to contact the same person or use the same electronic system for Tenant Events reservation requests. Reservation requests shall not be unreasonably withheld, conditioned, or delayed. During events held by non-profit or community organizations, event attendees and event volunteers and staff shall be permitted to park in the surface parking lot at no charge. In the event of planned maintenance or a Tenant Event during which the Front Plaza Easement Area and/or Courtyard Easement Area will be closed, Owner shall post signs within the Front Plaza Easement Area and/or Courtyard Easement Area at least forty-eight (48) hours prior to the closure for a Tenant Event or for planned maintenance. In the case of an emergency or repairs requiring attention within fortyeight (48) hours, Owner shall post signs to inform the public of the closure and secure the area.

7.f
October 23, 2023 Packet Pg. 158
52 6. Term. This POPA Agreement will commence immediately upon the Effective Date and will continue in perpetuity until and unless terminated by an agreement executed, acknowledged and recorded by the City or terminated according to the provisions of Section 7 of this POPA Agreement.

7. Termination. This POPA Agreement shall terminate in the event that (i) the Project is demolished or (ii) the Project undergoes a substantial change that is not already permitted under the Project Approvals and public access to the Easement Areas cannot be maintained by modifying the boundaries of the Easement Areas. Notwithstanding the foregoing, this POPA Agreement shall not terminate in the event of demolition and reconstruction of any building or buildings in the Project following a casualty. This POPA Agreement shall terminate with respect to only the Front Plaza Easement or only the Courtyard Easement Area if the Project undergoes a substantial change that is not already permitted under the Project Approvals and public access to the Front Plaza Easement Area or the Courtyard Easement Area cannot be maintained by modifying the boundaries of the Front Plaza Easement or the Courtyard Easement.

8. Insurance. Owner shall obtain and maintain insurance against claims for injuries to persons or damage to property which may arise out of any manner including (a) any injury to or death of any person or damage to or destruction of any property occurring in, on or about the Easement Areas, or any part thereof, whether such injury, death, damage or destruction is caused by the person or property of the Owner, representatives, employees or subcontractors. The insurance carrier is required to maintain an A.M. Best rating of not less than “A-:VII”. a. Coverages and Limits. Owner, at its sole expense, shall maintain the types of coverages and minimum limits indicated below, unless otherwise approved by City in writing. These minimum amounts of coverage will not constitute any limitations or cap on Owner's indemnification obligations under this POPA Agreement. (i) Commercial General Liability Insurance. Owner shall maintain occurrence based coverage with limits not less than $2,000,000 per occurrence. If the submitted policies contain aggregate limits, such limits will apply separately to the Services, project, or location that is the subject of this POPA Agreement or the aggregate will be twice the required per occurrence limit. The Commercial General Liability insurance policy shall be endorsed to name the City, its officers, agents, employees and volunteers as additional insureds, and to state that the insurance will be primary and not contribute with any insurance or self-insurance maintained by the City. (ii) Business Automobile Liability Insurance. Owner shall maintain coverage with limits not less than $1,000,000 per each accident for owned, hired and nonowned automobiles. (iii) Workers' Compensation and Employer's Liability Insurance. Owner shall maintain coverage as required by the California Labor Code and Employer’s Liability limits with limits not less than $1,000,000 per each accident for bodily injury or disease. The Worker’s Compensation policy shall contain an endorsement stating that the insurer waives any right to subrogation against the City, its officers, agents, employees, and volunteers.

7.f
October 23, 2023 Packet Pg. 159
53 b. Notice of Cancellation. The Owner's obligations under this Section shall survive the termination of this POPA Agreement and will not be canceled without Owner providing thirty (30) days prior written notice to City sent pursuant to the Notice provisions of this POPA Agreement.
c. Providing Certificates of Insurance and Endorsements. Prior to City’s execution of this POPA Agreement, Owner shall provide to City certificates of insurance and abovereferenced endorsements sufficient to satisfaction of City’s Risk Manager. In no event shall Owner commence any work or provide any Services under this POPA Agreement until certificates of insurance and endorsements have been accepted by City’s Risk Manager.
d. Failure to Maintain Coverage. If Owner fails to comply with these insurance requirements, then City will have the option to declare Owner in default. e. Submission of Insurance Policies. City reserves the right to require, at any time, complete copies of any or all required insurance policies and endorsements.

9. Indemnification. Owner agrees to indemnify, defend, and hold harmless the City, and each of its councilmembers, commissioners, officers, employees, representatives, agents, and contractors (“Indemnified Parties”), from and against any and all demands, claims, legal or administrative proceedings, losses, costs, penalties, fines, liens, judgments, damages and liabilities of any kind (“Claims”), arising in any manner out of (a) any injury to or death of any person or damage to or destruction of any property occurring in the Front Plaza Easement Area or the Courtyard Easement Area, whether such injury, death, damage or destruction is caused by the person or property of the Owner, its officers, directors, members, employees, agents, consultants, contractors or subcontractors (collectively, “Agents”), members of the public, Agent’s invitees, guests or visitors (collectively, “Invitees”), or third persons, relating to any use or activity under this POPA Agreement, (b) the use of the Easement Areas or any activities conducted thereon by the Owner, its Agents or Invitees, or third persons, relating to any use or activity under this POPA Agreement, (c) any release or discharge, or threatened release or discharge, of any Hazardous Material caused or allowed by the Owner, its Agents or Invitees, on, in, under or about the Front Plaza Easement Area or the Courtyard Easement Area, any improvements or into the environment, or (d) any failure by the Owner to faithfully observe or perform any terms, covenants or conditions of this POPA Agreement; except to the extent of Claims resulting from the negligence or willful misconduct of any Indemnified Parties. The foregoing indemnity shall include, without limitation, reasonable attorneys', experts’ and consultants' fees and costs, investigation and remediation costs and all other reasonable costs and expenses incurred by the Indemnified Parties. The Owner's obligations under this Section shall survive the termination of this POPA Agreement. Indemnified Parties shall have no liability to the Owner or any of the Owner’s Agents or Invitees as the result of damage or loss to property or injury or death to any such person arising on the Front Plaza Easement Area or the Courtyard Easement Area or out of the Owner’s use of the Front Plaza

7.f
October 23, 2023 Packet Pg. 160
54 Easement Area or the Courtyard Easement Area, except to the extent caused by the negligence or willful misconduct of any Indemnified Parties.

10. Miscellaneous Provisions.
a. Entire Agreement/Integration, Amendments, Recitals. This POPA Agreement contains the entire understanding and agreement of the Parties. This POPA Agreement may be altered, amended or modified only by an instrument in writing, executed by the City and Owner, or fee title owner of the Property. All recitals set forth above are incorporated by reference into this POPA Agreement. The Parties acknowledge that this Agreement has been executed initially pursuant to the terms of the Development Agreement, but the Development Agreement will terminate and have no further force or effect as to the terms of this POPA Agreement upon its execution. In the event of any inconsistency between the Development Agreement and this POPA Agreement, upon execution, this POPA Agreement controls.
b. Counterparts. This POPA Agreement may be executed in one or more counterparts, each of which shall, for all purposes, be deemed an original and all such counterparts, taken together, shall constitute one and the same instrument. c. Recitals; Attachments. The Recitals above and Attachments attached hereto are incorporated herein by reference.
d. Binding on Successors and Assigns. Owner’s Property is to be burdened by, and City is to be benefited by, the provisions of this POPA Agreement pertaining to the grant of Easement, and such Property shall be held, conveyed, hypothecated, encumbered, leased, rented, used, occupied, and improved subject to the foregoing easements, limitations, restrictions, obligations and conditions. All provisions of this POPA Agreement shall run with the land and be binding upon all parties having or acquiring any right, title, or interest in the Easement Areas, and shall be binding upon and inure to the benefit of the City and its and their successors and assigns. e. Partial Invalidity. If any term or provision of this POPA Agreement or the application of it to any person or circumstance shall to any extent be invalid or unenforceable, the remainder of this POPA Agreement or the application of such term or provision to persons or circumstances, other than those as to which it is invalid or unenforceable, shall not be affected thereby, and each term and provision of this POPA Agreement shall be valid and shall be enforced to the extent permitted by law. f. Not a Public Dedication. Except as expressly provided herein, nothing herein contained shall be deemed to be a gift or dedication of the Easement Areas or any other portion of Owner’s Property to the general public or for any public purpose whatsoever, it being the intention of the parties that this POPA Agreement shall be limited to and for the purposes herein expressed.

11. Exhibits; Attachments. The following attachments are attached to this POPA Agreement and are hereby incorporated herein by this reference for all purposes as if set forth herein in full:

7.f
October 23, 2023 Packet Pg. 161
55 Exhibit A Description of Property
Exhibit B.1 Legal Description of Front Plaza Easement Area Exhibit B.2 Legal Description of the Courtyard Easement Area

12. Attorneys’ Fees. Should any legal action be brought by any party with respect to this POPA Agreement, the prevailing party shall be entitled to recover from the non-prevailing party its reasonable attorney’s fees and such other costs as may be found by the court.

13. Joint and Several Liability. If more than one person or entity is included in the definition of Owner, the liability of all such persons hereunder shall be joint and several.

IN WITNESS WHEREOF, the City and Owner have executed this POPA Agreement as of the POPA Agreement Effective Date.

CITY
CITY OF SAN CARLOS, a municipal corporation
By: __________________________________
[Signature must be notarized]
ATTEST:

By: ____________________________
APPROVED AS TO FORM:

By: ____________________________
OWNER

THE SOBRATO FAMILY FOUNDATION,
a California nonprofit public benefit corporation
By: _______________________________
Name: _____________
Its: ______________
[Signature must be notarized]

7.f
October 23, 2023 Packet Pg. 162
56 Exhibit E
When Recorded, Mail to:

City of San Carlos
600 Elm Street
San Carlos, California 94070
Attn: City Clerk
This Instrument Benefits City Only.

No Fee Required. Gov. C. 27383
SPACE ABOVE THIS LINE FOR RECORDER’S USE
APN: ____

PUBLIC PARKING AGREEMENT
This Public Parking Agreement (“Agreement”) is made and executed as of ___________ (“Effective Date”) by and between _______ (“Owner”) and the CITY OF SAN CARLOS, a California municipal corporation (“City”). Owner and City are referred to herein individually as a “Party” and collectively as the “Parties.”

RECITALS
WHEREAS, Owner is the current fee owner of that certain real property consisting of approximately 3.4 acres located within the City of San Carlos, County of San Mateo, State of California, designated as APNs 046-133-160, 046-134-050, 046-134-060, 046-135-010, 046-135- 020, 046-135-030, 046-138-040, 046-182-100, 046-182-110 and 046-182-150 and legally described in Exhibit “A”, attached hereto and incorporated herein by reference (the “Property”).

WHEREAS, the Property is being developed as a mixed-use and R&D/life sciences development project consisting of approximately 339,170 gross square feet of office, R&D and life sciences uses in two buildings, two levels of below-grade parking and a front plaza and central courtyard (the “Project”).

WHEREAS, on [_________], the City Council of the City of San Carlos adopted Ordinance No. [_________], approving a Development Agreement by and between City and Owner (“Development Agreement”) and issued several other approvals identified in the Development Agreement (“Project Approvals”), subject to certain conditions of approval (“Conditions”).

WHEREAS, the Development Agreement requires the Owner to provide privately owned, publicly accessible open space within the Project and there will be a retail tenant that will be open to the public pursuant to a Privately Owned Publicly Accessible Open Space Easement and Maintenance Agreement (“POPA Agreement”). The public will need the right to park in the Project to enjoy the privately owned, publicly accessible open space and to visit the retail tenant in the Project.

7.f
October 23, 2023 Packet Pg. 163
57 WHEREAS, the Development Agreement requires Owner and City to execute a parking agreement under which Owner will share the Project’s commercial parking with the public by offering nightly and weekend public parking in the surface parking lot.

WHEREAS, the Parties desire to execute and record this Agreement to make the Project’s commercial parking available to the public upon the terms and conditions stated below to satisfy the requirements of the Development Agreement.

NOW, THEREFORE, in consideration of the foregoing and for other good and valuable consideration, the receipt and adequacy of which are acknowledged, the Parties hereby agree as follows:

1. Parking Terms and Conditions.

1.1. Public Use of Surface Parking. The surface parking lot, together with those areas necessary for ingress and egress to the surface parking lot as more particularly described in Exhibit B (collectively, the “Public Parking Area”), shall be available for use by the general public during the Hours of Public Use (as said term is defined below). The Public Parking Area shall include one dual head electric vehicle charging hub to provide two (2) charging stations and Owner shall designate two (2) parking spaces for vehicles using the charging stations. Owner may modify the Public Parking Area from time to time, in its sole discretion, upon providing reasonable advance notice to City of such modifications, provided however, that nothing herein limits the Owner’s obligation to comply with the requirements to obtain building permits, and/or City approval in its regulatory capacity of the modifications, if applicable. Owner shall designate seven (7) spaces within the Public Parking Area (“Plaza Public Parking Spaces”) to be available for use by members of the public visiting the Front Plaza, Courtyard, or the retail tenant during (i) the hours that any of the publicly accessible open spaces or the retail tenant are open to the public and (ii) the Hours of Public Use. The Plaza Public Parking Spaces shall be marked with conspicuous signage.

1.2. Hours of Public Use. The Public Parking Area shall be open to the general public Monday through Friday from 6:00 p.m. to 11:00 p.m.; and Saturday, Sunday, and Federal holidays from sunrise to 11:00 p.m. and during such other hours that Owner and City have agreed to grant a non-profit or community organization the right to hold an event in the courtyard in the Project pursuant to the POPA Agreement (collectively the “Hours of Public Use”). At all other times, Owner shall have exclusive control over the Public Parking Area for the exclusive use of the Owner, Owner’s tenants, and the guests, licensees, employees, agents, servants and representatives of Owner and Owner’s tenants.

Owner shall post multiple conspicuous signs, as approved by the City, in the Public Parking Area to inform the public of the Hours of Public Use.

1.3. Parking Rates. Owner shall make the Public Parking Area available at no cost to the public. Owner shall be free to establish parking rates for the other parking areas in the Project in its sole and absolute discretion, and Owner shall have the right to install

7.f
October 23, 2023 Packet Pg. 164
58 any access control and fee collection mechanisms it deems necessary or prudent to restrict ingress and egress to and from such other parking areas.

1.4. Independent Parking Management; Security. In its sole discretion, Owner may contract with, or grant a concession to, third-party entities to staff, operate, and/or provide security in the Public Parking Area and the other parking areas of the Project.

2. Maintenance of Public Parking Area. During the term of this Agreement, Owner shall maintain the Public Parking Area in good condition. All Public Parking Area improvements shall be repaired or replaced with materials, apparatus and facilities of at least equal quality of the materials, apparatus and facilities at initial construction of the Public Parking Area. Owner may temporarily limit or close the Public Parking Area to perform maintenance, repair and replacement activities.

3. Term; Termination. The term of this Agreement shall commence on the Effective Date and shall automatically terminate on the date at which the Property is no longer operating as the Project as defined above. Owner’s obligation to make the Public Parking Area available to the public under this Agreement shall commence upon City’s issuance of a final certificate of occupancy for the South Building.

4. Insurance. During the term of this Agreement, Owner shall maintain Commercial General Liability Insurance coverage with a combined single limit of at least $_,000,000 per occurrence/aggregate. Owner shall furnish City with certificates of insurance evidencing that City is included as an additional insured on the Commercial General Liability policy [to be completed prior to execution in consultation with the Parties’ risk management].

5. Mortgagee Protection. No violation or breach of the covenants, conditions, restrictions, provisions or limitations contained in this Agreement shall defeat or render invalid or in any way impair the lien or charge of any mortgage, deed of trust or other financing or security instrument; provided, however, that any successor of Owner to the Property shall be bound by such remaining covenants, conditions, restrictions, limitations and provisions, of this Agreement whether such successor's title was acquired by foreclosure, deed in lieu of foreclosure, trustee's sale or otherwise. In the event of a default on the part of Owner hereunder, City shall give notice to any beneficiary of a deed of trust or mortgage whose address has been furnished to City, and City shall offer such beneficiary or mortgagee a reasonable opportunity to cure the default, including obtaining possession of the Property by power of sale or a judicial foreclosure, if the beneficiary has such authority and such a remedy is necessary to effect a cure.

6. Estoppel Certificates. Any party to this Agreement shall, promptly upon the request of any other party, execute, acknowledge and deliver to or for the benefit of any other party, at any time, from time to time, and at the expense of the party, requesting a certificate as herein below described, promptly upon request, its certificate certifying (l) that this Agreement is unmodified and in full force and effect (or, if there have been modifications, that this Agreement is in full force and effect, as modified, and stating the modifications), (2) whether there are then existing any charges, offsets or defenses against .the enforcement of any agreement, covenant or condition hereof on the part of the party requesting the certificate to be performed or observed (and, if so, specifying the same), (3) whether there are then existing any defaults on the part of the parry

7.f
October 23, 2023 Packet Pg. 165
59 requesting the certificate known to the parry delivering the certificate in the performance or observance of any agreement, covenant or condition hereof to be performed or observed and whether any notice has been given of any default which has not been cured (and, if so, specifying the same), and (4) any other matters reasonably requested.

7. Indemnification. Owner shall be solely liable for the operation, upkeep and maintenance of the Public Parking Area and all other parking areas in the Project. Owner, to the fullest extent permitted by law, shall indemnify, defend, and hold harmless the City, its officers, agents, and employees from any and all liabilities, claims, demands, damages, or costs resulting from or growing out of such Owner’s acts or omissions related to the operation, upkeep and maintenance of the Public Parking Area and other parking areas in the Project, except to the extent that any such liabilities are the result of the gross negligence or willful misconduct of City, its officers, agents, or employees. The Owner’s duty to indemnify and hold harmless City includes the duty to defend as set forth in Civil Code section 2778. Owner’s indemnification obligations under this Section shall survive expiration or termination of this Agreement.

8. Notices. If at any time after the execution of this Agreement it becomes necessary for one of the Parties hereto to serve any notice, demand or communication upon the other Party, such notice, demand or communication shall be in writing and shall be served personally or by depositing the same in the certified United States mail, return receipt requested, postage prepaid, and shall be addressed to:

If to City:
________________
________________
________________
If to Owner:
________________
________________
________________
With a copy to:
________________
________________
________________

9. Entire Agreement. This Agreement constitute the entire agreement of the parties hereto with respect to the subject matter hereof and thereof, and supersede all prior agreements and understandings of the parties, oral and written, with respect to the subject matter hereof.

10. Amendments. This Agreement may not be amended, modified, and/or removed unless otherwise approved and agreed upon by a written agreement between City and Owner (or subsequent owner of the Project), and recorded with the County Recorder’s Office.

7.f
October 23, 2023 Packet Pg. 166
60 11. Successors and Assigns. The terms and conditions of this Agreement shall be binding upon and shall inure to the benefit of each of the Parties hereto, and their respective heirs, legal representatives, successors and assigns.

12. Force Majeure. All obligations in this Agreement shall not be deemed to be in default and all performance shall be extended where such delays are due to: war; insurrection; strikes and labor disputes; lockouts; riots; earthquakes; floods; fires; casualties; condemnation; acts of God; acts of terrorism or the public enemy; epidemics; quarantine restrictions; litigation and arbitration, including court delays or compliance with court orders; environmental conditions; acts or omissions of the other Party; or acts or failures to act of any public or governmental agency or entity (except that acts or failures to act of City shall not excuse performance by City); or moratorium. An extension of time for any such cause shall be for the period of the enforced delay and shall commence to run from the time of the commencement of the cause, if notice by the Party claiming such extension is sent to the other Party within ninety (90) days of such Party’s actual knowledge of the commencement of the cause.

13. Entire Agreement; Integration. This Agreement contains the entire understanding and agreement of the Parties. The Parties acknowledge that this Agreement has been executed initially pursuant to the terms of the Development Agreement, but the Development Agreement will terminate and have no further force or effect as to the terms of this Agreement upon its execution. In the event of any inconsistency between the Development Agreement and this Agreement, once executed, this Agreement controls.

14. Not a Public Dedication. Except as expressly provided herein, nothing herein contained shall be deemed to be a gift or dedication of the Public Parking Area or any other portion of Owner’s Property to the general public or for any public purpose whatsoever, it being the intention of the parties that this Agreement shall be limited to and for the purposes herein expressed.

15. Governing Law. This Agreement shall be governed and construed in accordance with the laws of the State of California.

16. Severability. If any of the provisions contained in this Agreement shall for any reason be held to be invalid, illegal, or unenforceable in any respect, then such provision(s) shall be deemed severable from the remaining provision(s) contained in this Agreement, and this Agreement shall be construed as if such invalid, illegal, or unenforceable item had never been contained herein.

17. Recordation. This Agreement shall be recorded in the Official Records of the County of San Mateo following execution by the Parties.

IN WITNESS WHEREOF, the Parties execute this Agreement as of the date set forth above.
[Signature Pages to Follow]

7.f
October 23, 2023 Packet Pg. 167
61 OWNER:

By: _____________________________
Name: _____________________________
Its: _____________________________
CITY:

CITY OF SAN CARLOS, a California municipal corporation
________________________________
City Manager
APPROVED AS TO CONTENT:
________________________________
Community Development Director
APPROVED AS TO FORM:

By:

Name:

Its: City Attorney

7.f
October 23, 2023 Packet Pg. 168
62 ARTICLE 13

ACKNOWLEDGMENT
State of California )
)
County of )
On before me,
____________________________________________________
(insert name and title of the officer)
personally appeared _____________________________________________________ who proved to me on the basis of satisfactory evidence to be the person(s) whose name(s) is/are subscribed to the within instrument and acknowledged to me that he/she/they executed the same in his/her/their authorized capacity(ies), and that by his/her/their signature(s) on the instrument the person(s), or the entity upon behalf of which the person(s) acted, executed the instrument.

I certify under PENALTY OF PERJURY under the laws of the State of California that the foregoing paragraph is true and correct.

WITNESS my hand and official seal.

Signature ______________________________________ (Seal) A notary public or other officer completing this certificate verifies only the identity of the individual who signed the document to which this certificate is attached, and not the truthfulness, accuracy, or validity of that document.

7.f
October 23, 2023 Packet Pg. 169
63 EXHIBIT A
Property Legal Description

7.f
October 23, 2023 Packet Pg. 170
Order Number: NCS-1033730-SC
Page Number: 9
First American Title Insurance Company

LEGAL DESCRIPTION
Real property in the City of San Carlos, County of San Mateo, State of California, described as follows:

PARCEL ONE:

BEGINNING AT A POINT ON THE NORTHEASTERLY LINE OF THE COUNTY ROAD LEADING FROM SAN CARLOS TO REDWOOD CITY, DISTANT THEREON SOUTH 42° 22' 30" EAST 706.74 FEET FROM THE

MOST WESTERLY CORNER OF THAT TRACT OF LAND KNOWN AS SPEEDWAY ACRES CONVEYED TO ASA E. HULL FROM C. S. MORTON, ET AL., BY DEED DATED JUNE 16, 1924 AND RECORDED IN BOOK 128 AT PAGE 107 (23249A), OFFICIAL RECORDS OF SAN MATEO COUNTY THENCE ALONG THE NORTHEASTERLY LINE OF SAID COUNTY ROAD, SOUTH 42° 22' 30" EAST 206.41 FEET THENCE LEAVING THE LAST MENTIONED LINE, NORTH 48° 53' EAST 234.56 FEET TO THE SOUTHWESTERLY LINE OF THE LAND DESCRIBED AS PARCEL 2 IN THE DEED TO SOUTHERN PACIFIC RAILROAD COMPANY RECORDED JUNE 18, 1926 IN BOOK 243 AT PAGE 17 (62690A), OFFICIAL RECORDS OF SAN MATEO COUNTY THENCE ALONG THE LAST MENTIONED LINE, NORTH 42° 22' 30" WEST 206.41 FEET TO A POINT WHICH BEARS NORTH 48° 53' EAST FROM THE POINT OF BEGINNING; THENCE SOUTH 48° 53' WEST 234.56 FEET TO THE POINT OF BEGINNING.

PARCEL TWO:

BEGINNING AT A POINT ON THE NORTHEASTERLY LINE OF THE COUNTY ROAD LEADING FROM SAN CARLOS TO REDWOOD CITY, DISTANT THEREON SOUTH 42° 22' 30" EAST 913.16 FEET FROM THE

MOST WESTERLY CORNER OF THAT TRACT OF LAND KNOWN AS SPEEDWAY ACRES CONVEYED TO ASA E. HULL FROM C. B. MORTON, ET AL., BY DEED DATED JUNE 16, 1924 AND RECORDED IN BOOK 128 AT PAGE 107 (23249A), OFFICIAL RECORDS OF SAN MATEO COUNTY; THENCE FROM SAID POINT OF BEGINNING LEAVING THE NORTHEASTERLY LINE OF SAID COUNTY ROAD, NORTH 48° 43' EAST 234.56 FEET TO THE SOUTHWESTERLY LINE OF THE LAND DESCRIBED AS PARCEL 2 IN THE DEED TO SOUTHERN PACIFIC RAILROAD COMPANY RECORDED JUNE 18, 1926 IN BOOK 243 AT PAGE 17 (62690A), OFFICIAL RECORDS OF SAN MATEO COUNTY THENCE ALONG THE LAST MENTIONED LINE, SOUTH 42° 22' 30" EAST 56.68 FEET TO THE NORTHWESTERLY LINE OF COMMERCIAL WAY AS

ESTABLISHED BY DEED TO THE CITY OF SAN CARLOS, A MUNICIPAL CORPORATION, RECORDED OCTOBER 12, 1973 IN BOOK 6485 AT PAGE 501 (82827AG) OFFICIAL RECORDS OF SAN MATEO

COUNTY THENCE ALONG SAID NORTHWESTERLY LINE OF COMMERCIAL WAY AND THE SOUTHWESTERLY PROLONGATION THEREOF, SOUTH 48° 53' WEST 234.56 FEET TO THE

NORTHEASTERLY LINE OF SAID COUNTY ROAD THENCE ALONG THE LAST MENTIONED LINE, NORTH 42° 12' 30" WEST 56.68 FEET TO THE POINT OF BEGINNING.

PARCEL THREE:

BEING ALL OF PARCEL 2 AS DESCRIBED IN THE DEED FROM CALIFORNIA CONCRETE PRODUCTS AND ASA E. HULL TO SOUTHERN PACIFIC RAILROAD COMPANY RECORDED JUNE 18, 1926 IN VOLUME 243 OF OFFICIAL RECORDS AT PAGE 17 (243 O.R. 17); AND A PORTION OF PARCEL 2 AS DESCRIBED IN THE DEED FROM K.A. WINTER ET. AL. TO SOUTHERN PACIFIC RAILROAD COMPANY RECORDED JUNE 18, 1926 IN VOLUME 243 OF OFFICIAL RECORDS AT PAGE 12 (243 O.R. 12); BEING MORE PARTICULARLY DESCRIBED AS FOLLOWS:

BEGINNING AT THE MOST SOUTHERLY CORNER OF SAID PARCEL 2 OF SAID 243 O.R. 17; THENCE ALONG THE SOUTHWESTERLY LINE OF SAID PARCEL NORTH 42°22'30" WEST 293.10 FEET TO THE MOST SOUTHERLY CORNER OF SAID PARCEL 2 OF SAID 243 O.R. 12; THENCE ALONG THE SOUTHWESTERLY LINE OF SAID PARCEL NORTH 42°22'30" WEST 56.70 FEET TO

7.f
October 23, 2023 Packet Pg. 171
Order Number: NCS-1033730-SC
Page Number: 10
First American Title Insurance Company
THE BEGINNING OF A TANGENT CURVE TO THE LEFT HAVING A RADIUS OF 397.97 FEET; THENCE NORTHWESTERLY ALONG SAID CURVE THROUGH A CENTRAL ANGLE OF 1°29'08" A DISTANCE OF 10.32 FEET TO THE SOUTHEASTERLY LINE OF THE LANDS AS DESCRIBED IN THE QUITCLAIM DEED FROM UNION PACIFIC RAILROAD COMPANY TO KELLOGG ET. AL. RECORDED MAY 31, 2002 IN DOCUMENT NUMBER 2002-106037, OFFICIAL RECORDS OF SAN MATEO COUNTY; THENCE ALONG SAID SOUTHEASTERLY LINE NORTH 48°53'00" EAST 17.01 FEET TO A POINT ON THE NORTHEASTERLY LINE OF SAID PARCEL 2 OF SAID 243 O.R. 12; SAID POINT LYING A CURVE CONCAVE TO THE SOUTHWEST HAVING A RADIUS OF 414.97 FEET; A RADIAL LINE TO SAID POINT BEARING NORTH 46°15'05" EAST;
THENCE SOUTHEASTERLY ALONG SAID CURVE THROUGH A CENTRAL ANGLE OF 1°22'25" A DISTANCE OF 9.95 FEET;
THENCE TANGENT FROM SAID CURVE ALONG SAID NORTHEASTERLY LINE SOUTH 42°22'30" EAST

57.07 FEET TO THE MOST NORTHERLY CORNER OF SAID PARCEL 2 OF SAID 243 O.R. 17; THENCE ALONG THE NORTHEASTERLY LINE OF SAID PARCEL SOUTH 42°22'30" EAST 293.10 FEET TO THE SOUTHEASTERLY CORNER OF SAID PARCEL;
THENCE ALONG THE SOUTHEASTERLY LINE OF SAID PARCEL SOUTH 48°53'00" WEST 17.00 FEET TO THE POINT OF BEGINNING.

EXCEPTING THEREFROM ALL MINERALS AND ALL MINERAL RIGHTS OF EVERY KIND AND CHARACTER

NOW KNOWN TO EXIST OR HEREAFTER DISCOVERED UNDERLYING THE PROPERTY, INCLUDING,

WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, OIL AND GAS AND RIGHTS THERETO,

TOGETHER WITH THE SOLE, EXCLUSIVE AND PERPETUAL RIGHT TO EXPLORE FOR, REMOVE AND

DISPOSE OF SAID MINERALS BY ANY MEANS OR METHODS SUITABLE TO GRANTOR, ITS SUCCESSORS

AND ASSIGNS, BUT WITHOUT ENTERING UPON OR USING THE SURFACE OF THE PROPERTY, AND IN

SUCH MANNER AS NOT TO DAMAGE THE SURFACE OF THE PROPERTY, OR TO INTERFERE WITH THE

USE THEREOF BY GRANTEE, HER HEIRS AND ASSIGNS, AS RESERVED IN QUITCLAIM DEED RECORDED OCTOBER 26, 2007 AS INSTRUMENT NO. 2007-154663 OF OFFICIAL RECORDS.

PARCEL FOUR:

BEGINNING AT THE MOST SOUTHERLY CORNER OF THAT CERTAIN 20 ACRE TRACT DESCRIBED IN THE AGREEMENT BETWEEN ASA B. HULL AND I.H. WINTER ET AL, RECORDED NOVEMBER 24, 1925 IN BOOK 201 OF OFFICIAL RECORDS OF SAN MATEO COUNTY AT PAGE 290; THENCE FROM SAID POINT OF BEGINNING ALONG THE SOUTHEASTERLY LINE OF SAID 20 ACRE TRACT, NORTH 48°53' EAST 230.00 FEET; THENCE LEAVING SAID SOUTHEASTERLY LINE AND RUNNING ACROSS SAID 20 ACRE TRACT, NORTH 42° 22' 30" WEST 90.02 FEET AND SOUTH 48° 53' WEST 230.00 FEET TO A POINT ON THE NORTHEASTERLY LINE OF THE COUNTY ROAD LEADING FROM REDWOOD CITY TO CARLOS; THENCE ALONG SAID NORTHEASTERLY LINE OF SAID COUNTY ROAD, SOUTH 42° 22' 30" EAST 90.03 FEET TO THE POINT OF BEGINNING.

PARCEL FIVE:

BEGINNING AT A POINT ON THE NORTHEASTERLY LINE OF THAT CERTAIN COUNTY ROAD LEADING

FROM REDWOOD CITY TO SAN CARLOS, SAID POINT OF BEGINNING BEING DISTANT ALONG SAID NORTHEASTERLY LINE OF SAID COUNTY ROAD NORTH 42° 22’ 30” WEST 180.04 FEET FROM THE MOST SOUTHERLY CORNER OF THAT CERTAIN 20 ACRE TRACT DESCRIBED IN AGREEMENT BETWEEN ASA E. HULL AND K.A. WINTER, ET AL, SAID AGREEMENT BEING FILED FOR RECORD NOVEMBER 24, 1925 IN VOLUME 201 OF OFFICIAL RECORDS AT PAGE 290, RECORDS OF SAN MATEO COUNTY, CALIFORNIA; THENCE FROM SAID POINT OF BEGINNING ALONG SAID NORTHEASTERLY LINE OF SAID

7.f
October 23, 2023 Packet Pg. 172
Order Number: NCS-1033730-SC
Page Number: 11
First American Title Insurance Company
COUNTY ROAD NORTH 42° 22’ 30” WEST 90.02 FEET TO A POINT WHERE SAID NORTHEASTERLY LINE OF SAID COUNTY ROAD IS INTERSECTED BY THE SOUTHEASTERLY LINE OF A 50 FOOT PRIVATE ROAD RUNNING THROUGH ABOVE DESCRIBED 20 ACRE TRACT; THENCE ALONG SAID SOUTHEASTERLY LINE OF SAID 50 FOOT ROAD NORTH 48° 53’ EAST 230 FEET; THENCE LEAVING SAID SOUTHEASTERLY LINE OF SAID 50 FOOT PRIVATE ROAD AND RUNNING SOUTH 42° 22’ 30” EAST 90.02 FEET AND SOUTH 48° 53’ WEST 230.0 FEET TO THE POINT OF BEGINNING.

PARCEL SIX:

BEGINNING AT A POINT ON THE NORTHEASTERLY LINE OF THE OLD COUNTY ROAD FROM REDWOOD

CITY TO SAN CARLOS (SAID ROAD LYING NORTHEASTERLY OF THE TRACKS OF THE SOUTHERN

PACIFIC RAILROAD), SAID POINT OF BEGINNING BEING DISTANT ALONG SAID NORTHEASTERLY LINE OF SAID ROAD, NORTH 42° 22’ 30” WEST 90.02 FEET FROM THE MOST SOUTHERLY CORNER OF THAT CERTAIN 20 ACRE TRACT DESCRIBED IN AGREEMENT BETWEEN ASA E. HULL AND K.A. WINTER, ET AL, RECORDED NOVEMBER 24, 1925 IN VOLUME 201 OF OFFICIAL RECORDS AT PAGE 290, RECORDS OF SAN MATEO COUNTY, CALIFORNIA; THENCE FROM SAID POINT OF BEGINNING ALONG SAID NORTHEASTERLY LINE OF SAID COUNTY ROAD, NORTH 42°22’ 30” WEST 90.02 FEET; THENCE NORTH 48° 53’ EAST 230.0 FEET; THENCE SOUTH 42°22’ 30” EAST 90.02 FEET; THENCE SOUTH 48°53’ WEST 230.0 FEET TO THE POINT OF BEGINNING.

PARCEL SEVEN:

A PARCEL OF LAND SITUATE IN THE CITY OF SAN CARLOS, COUNTY OF SAN MATEO, STATE OF CALIFORNIA, BEING PARCEL THREE AS DESCRIBED IN A DEED RECORDED NOVEMBER 26, 1991 IN DOCUMENT NUMBER 91155625 OFFICIAL RECORDS OF SAN MATEO COUNTY, MORE PARTICULARLY DESCRIBED AS FOLLOWS:

BEGINNING AT A POINT ON THE SOUTHEASTERLY LINE OF THAT CERTAIN 20 ACRES TRACT DESCRIBED IN THE AGREEMENT BETWEEN ASA E. HULL AND K.A. WINTER, ET AL, RECORDED NOVEMBER 24, 1925 IN BOOK 201 OFFICIAL RECORDS OF SAN MATEO COUNTY, PAGE 290, SAID POINT OF BEGINNING BEING DISTANT ALONG SAID SOUTHEASTERLY LINE NORTH 48° 53’ EAST 230.0 FEET FROM THE MOST SOUTHERLY CORNER OF SAID 20 ACRE TRACT; THENCE FROM SAID POINT OF BEGINNING ALONG SAID SOUTHEASTERLY LINE NORTH 48° 53’ EAST, 100.00 FEET, THENCE LEAVING SAID SOUTHEASTERLY LINE AND RUNNING ACROSS SAID 20 ACRE TRACT NORTH 41° 07’ WEST, 270.00 FEET OF THE SOUTHEASTERLY LINE OF A 50 FOOT PRIVATE ROAD RUNNING THROUGH THE ABOVE DESCRIBED 20 ACRE TRACT; THENCE ALONG SAID SOUTHEASTERLY LINE OF SAID 50 FOOT PRIVATE ROAD SOUTH 48° 53’ WEST, 105.93 FEET; THENCE LEAVING SAID SOUTHEASTERLY LINE OF SAID 50 FOOT ROAD SOUTH 42° 22’ 30” EAST, 270.06 FEET TO THE POINT OF BEGINNING.

EXCEPTING THEREFROM THAT PORTION OF THE ABOVE DESCRIBED PROPERTY WHICH LIES SOUTHEASTERLY OF A LINE PARALLEL TO AND 90.02 FEET MEASURED PERPENDICULARLY NORTHWESTERLY OF THE ABOVE SAID SOUTHEASTERLY LINE OF SAID 20 ACRE TRACT AND NORTHEASTERLY OF THE COURSE CALLED SOUTH 42° 22’ 30” EAST, 57.074 FEET AND THE NORTHWESTERLY EXTENSION THEREOF, AS SAID COURSE IS DESCRIBED IN PARCEL #2 OF THE ABOVE SAID DEED RECORDED JUNE 18, 1926 IN BOOK 243 OFFICIAL RECORDS OF SAN MATEO COUNTY PAGE 12.

ALSO EXCEPTING THEREFROM, THAT PORTION THEREOF LYING WITHIN THE PARCEL DESCRIBED IN

THE QUITCLAIM DEED FROM UNION PACIFIC RAILROAD COMPANY, A DELAWARE CORPORATION TO WANDA MAE ADAMS RECORDED OCTOBER 26, 2007 AS INSTRUMENT NO. 2007-154663 OF OFFICIAL RECORDS.

For reference purposes only:

7.f
October 23, 2023 Packet Pg. 173
Order Number: NCS-1033730-SC
Page Number: 12
First American Title Insurance Company
APN: 046-182-100 (affects Parcel One);
046-182-110 (affects Parcel Two);
046-182-150 (affects Parcel Three);
046-135-030 (affects Parcel Four);
046-135-010 (affects Parcel Five);
046-135-020 (affects Parcel Six);
046-135-040 (affects portion of Parcel Seven);
046-134-050 (affects portion of Parcel Seven);
046-134-060 (affects portion of Parcel Seven);
and 046-133-160 (affects portion of Parcel Seven)
JPN:
046-018-182-04A
046-018-182-05A
046-013-135-03A
046-013-135-01A
046-013-135-02A
046-013-134-03A
046-013-133-016A

7.f
October 23, 2023 Packet Pg. 174
64 EXHIBIT B
Public Parking Area
[legal description or site plan]

7.f
October 23, 2023 Packet Pg. 175
65 Exhibit F

RECORDING REQUESTED BY
AND WHEN RECORDED MAIL TO:

Attn:
(Space Above for Recorder’s Use)
[FORM OF] ASSIGNMENT OF RIGHTS AND ASSUMPTION OF OBLIGATIONS

UNDER DEVELOPMENT AGREEMENT
(______________)

THIS ASSIGNMENT OF RIGHTS AND ASSUMPTION OF OBLIGATIONS UNDER DEVELOPMENT AGREEMENT (this “Assignment”) is made and entered into as of _________, 20__, by and between _______, a _________ (“Assignor”), and __________________, a ____________ (“Assignee”), and approved and agreed to by the City of ______, a ________ (“City”).

RECITALS
A. Assignor and City entered into that certain Development Agreement dated as of ______ for the _____ project, and recorded on _____ in the Official Records of the San Mateo County Recorder’s Office (“Official Records”) as Document No. _______, (the “Development Agreement”), with respect to approximately ____ acres of land within the City, as more particularly described in Exhibit A attached hereto (the “Property”).

B. Assignor and Assignee have entered into that certain Agreement for Purchase and Sale ____________ dated ____________ (as may be amended from time to time, the “Purchase Agreement”), pursuant to which Assignor intends to transfer to Assignee the Property.

Concurrently with transfer of the Property to Assignee, and solely in connection with such transfer in accordance with the Purchase Agreement, Assignor desires to assign to Assignee, and Assignee desires to accept from Assignor the rights, interests and obligations as Owner under the Development Agreement.

C. Section 10.1 of the Development Agreement provides that the Developer shall be released from its obligations under the Development Agreement upon the assignment of the Developer’s rights, interests and obligations under the Development Agreement if the City agrees to such release in writing, and Assignor wishes to memorialize that, upon the effective date of this Assignment, as set forth in Section 4 hereof, Assignor is hereby fully released from the duties and obligations of “Developer” with respect to the Development Agreement, including, without limitation, the Project Approvals, which release is hereby given by the City’s execution of this Assignment as provided below.

7.f
October 23, 2023 Packet Pg. 176
66 AGREEMENTS
NOW, THEREFORE, in consideration of the foregoing recitals and for the purposes and in consideration of the mutual covenants hereinafter contained, and for other good and valuable consideration, the receipt of which is hereby acknowledged, Assignor and Assignee agree as follows:

1. Defined Terms. All capitalized terms used but not defined in this Assignment shall have the meanings given to them in the Development Agreement.

2. Assignment and Assumption. Assignor hereby assigns to Assignee and Assignee hereby expressly and unconditionally assumes from Assignor, all rights, title, duties, interests and obligations under the Development Agreement.

3. Compliance with Assignment Requirements; Release. Approval of this Assignment by the City pursuant to Section 10.1 of the Development Agreement is an express condition precedent to the effectiveness of this Assignment. Each of Assignor and Assignee has complied with and satisfied all of the requirements and conditions under the Development Agreement with respect to assignment and assumption of the Assigned Interests, including, without limitation, those set forth in Section 10.1 of the Development Agreement, and all of the requirements and conditions under the Development Agreement for the release of Assignor from those obligations related to the Assigned Property and the Assigned Interests, set forth in Section

10.1 of the Development Agreement (collectively, the “Requirements”). Upon approval by the City pursuant to Section 10.1 of the Development Agreement, Assignor shall be fully released from all of the duties, obligations and liabilities of the “Developer” under the Development Agreement with respect to the Assigned Interests.

Assignee on behalf of itself and its successors and assigns, waives any right to recover from, and forever releases, acquits and discharges, Assignor and its directors, officers, employees and agents of and from any and all claims, demands, losses, liabilities, damages (including foreseeable and unforeseeable consequential damages), liens, obligations, interest, injuries, penalties, fines, lawsuits and other proceedings, judgments and awards and costs and expenses, (including, without limitation, reasonable attorneys’ fees and costs and consultants’ fees and costs) of whatever kind or nature, known or unknown, contingent or otherwise, whether direct or indirect, known or unknown, foreseen or unforeseen, that Assignee may now have or that may arise at any time on account of or in any way be connected with the Development Agreement, except as otherwise expressly set forth in the Purchase Agreement. This waiver is not intended to supersede or otherwise modify any terms of the Purchase Agreement.

In connection with the foregoing release, Assignee acknowledges that it is familiar with Section 1542 of the California Civil Code, which provides as follows:

A GENERAL RELEASE DOES NOT EXTEND TO CLAIMS WHICH THE CREDITOR

OR RELEASING PARTY DOES NOT KNOW OR SUSPECT TO EXIST IN HIS OR

HER FAVOR AT THE TIME OF EXECUTING THE RELEASE AND THAT, IF

KNOWN BY HIM OR HER, WOULD HAVE MATERIALLY AFFECTED HIS OR HER SETTLEMENT WITH THE DEBTOR OR RELEASED PARTY.

7.f
October 23, 2023 Packet Pg. 177
67 Assignee agrees that the release contemplated by this Section includes unknown claims.

Accordingly, Assignee hereby waives the benefits of Civil Code Section 1542, or under any other statute or common law principle of similar effect, in connection with the releases contained in this Section.

Assignor Assignee
Without limiting the foregoing and notwithstanding any contrary provision in the Development Agreement, City (i) acknowledges and agrees to the terms and conditions of this Assignment and that the Requirements have been satisfied, (ii) hereby fully releases Assignor, and Assignor is fully released, from all of the duties and obligations of the “Developer” under the Development Agreement and (iii) shall look solely towards Assignee with respect to performance, compliance and satisfaction of all covenants and obligations of Developer related to the Assigned Property.

4. Effective Date. Subject to the condition precedent set forth in Section 3 above, this Assignment shall be effective upon the later to occur of (i) the date all Parties have duly executed this Assignment and (ii) the date of the transfer of the Assigned Property to Assignee in accordance with the Purchase Agreement (the “Effective Date”). The Parties shall use a mutually acceptable escrow agent to record this Assignment Agreement and establish the Effective Date pursuant to mutually acceptable joint escrow instructions.

5. Acknowledgement of the Development Agreement and Project Approvals.

Assignee further agrees that: (i) Assignee has had adequate opportunity to obtain and review copies of the Development Agreement and Project Approvals, and all other documents and materials containing or relating to the terms and conditions of the development of the project; (ii) Assignee has read and understands all of the terms and conditions of said documents and materials; (iii) except as expressly set forth in the Purchase Agreement, Assignor has not made any representations or warranties with respect to the Assigned Property, the Project Approvals or any other aspect of development of the Property or the Development Agreement, and (iv) with such knowledge and understanding, which includes the nature and extent of the fees, taxes, assessments and other financial mechanisms and obligations described in such documents and materials, Assignee nevertheless has voluntarily, freely and knowingly assumed and agreed to perform all obligations and requirements and be bound by all of the provisions of such documents and materials.

6. Terms of Development Agreement and Purchase Agreement Not Affected. Except that Assignee shall be subject to, and Assignor shall be released from, the Development Agreement, the provisions of the Development Agreement shall remain in full force and effect and shall not be altered, amended or modified by this Assignment, nor shall any of the provisions of the Purchase Agreement be altered, amended or modified by this Assignment. In the event of any conflict between any provision of the Purchase Agreement and any provision of this Assignment, the provisions of this Agreement shall control.

7.f
October 23, 2023 Packet Pg. 178
68 7. Modifications. This Assignment may be amended, terminated or otherwise modified in any respect only by a writing duly executed on behalf of Assignor and Assignee and approved by the City.

8. Attorneys’ Fees. In the event of any controversy, claim, dispute, or litigation between the parties hereto to enforce or interpret any of the provisions of this Assignment or any right of either party hereto, the non-prevailing party to such litigation agrees to pay to the prevailing party all costs and expenses, including, without limitation, reasonable attorneys’ fees, incurred therein by the prevailing party, including, without limitation, fees incurred during a trial of any action and any fees incurred as a result of an appeal from a judgment entered in such litigation. To so recover, it shall not be necessary that the prevailing party prevail in each and every one of its claims. Rather, the amount of the award of attorneys’ fees shall, in the court’s discretion, reflect the degree to which the prevailing party or parties have prevailed in some of their claims.

9. Consent of City. By signature of the Community Development Director of the City below, the City approves and agrees to the assignment, assumption and release set forth in this Assignment. The City is a party to this Assignment solely respect to Section 3 and Section 4 hereof.

10. Governing Law. This Assignment shall be governed by and construed in accordance with the laws of California, as they apply to contracts executed in and to be carried out entirely within California.

11. Further Assurances. Each party to this Assignment, upon the request of any other party to this Assignment, will execute, acknowledge and deliver such further documents or instruments and perform such further acts as may be necessary, desirable or proper to carry out more effectively the purpose of this Assignment. Each of the individuals executing this Assignment certifies that he or she is duly authorized to do so.

12. Counterparts. This Assignment may be executed in one or more counterparts. All counterparts so executed shall constitute one agreement, binding on all parties, even though all parties are not signatory to the same counterpart.
[Signatures appear on the following page]

7.f
October 23, 2023 Packet Pg. 179
69 IN WITNESS WHEREOF, the parties hereto have executed this Assignment as of the date and year first above written.

ASSIGNOR:
__________, a ____________
By:

Name:

Its:

By:

Name:

Its:

ASSIGNEE:
______________________, a
________________________
By:

Name:

Its:

By:

Name:

Its:

ATTEST:

By:

APPROVED AS TO FORM:

By:

ACKNOWLEDGED AND APPROVED
TO BY CITY:

CITY OF ______, _________
By:

Name:

Its: ______________________________
[Signatures must be notarized]

7.f
October 23, 2023 Packet Pg. 180
70 EXHIBIT A

LEGAL DESCRIPTION OF THE PROPERTY
[to be inserted upon execution]

7.f
October 23, 2023 Packet Pg. 181
Order Number: NCS-1033730-SC
Page Number: 9
First American Title Insurance Company

LEGAL DESCRIPTION
Real property in the City of San Carlos, County of San Mateo, State of California, described as follows:

PARCEL ONE:

BEGINNING AT A POINT ON THE NORTHEASTERLY LINE OF THE COUNTY ROAD LEADING FROM SAN CARLOS TO REDWOOD CITY, DISTANT THEREON SOUTH 42° 22' 30" EAST 706.74 FEET FROM THE

MOST WESTERLY CORNER OF THAT TRACT OF LAND KNOWN AS SPEEDWAY ACRES CONVEYED TO ASA E. HULL FROM C. S. MORTON, ET AL., BY DEED DATED JUNE 16, 1924 AND RECORDED IN BOOK 128 AT PAGE 107 (23249A), OFFICIAL RECORDS OF SAN MATEO COUNTY THENCE ALONG THE NORTHEASTERLY LINE OF SAID COUNTY ROAD, SOUTH 42° 22' 30" EAST 206.41 FEET THENCE LEAVING THE LAST MENTIONED LINE, NORTH 48° 53' EAST 234.56 FEET TO THE SOUTHWESTERLY LINE OF THE LAND DESCRIBED AS PARCEL 2 IN THE DEED TO SOUTHERN PACIFIC RAILROAD COMPANY RECORDED JUNE 18, 1926 IN BOOK 243 AT PAGE 17 (62690A), OFFICIAL RECORDS OF SAN MATEO COUNTY THENCE ALONG THE LAST MENTIONED LINE, NORTH 42° 22' 30" WEST 206.41 FEET TO A POINT WHICH BEARS NORTH 48° 53' EAST FROM THE POINT OF BEGINNING; THENCE SOUTH 48° 53' WEST 234.56 FEET TO THE POINT OF BEGINNING.

PARCEL TWO:

BEGINNING AT A POINT ON THE NORTHEASTERLY LINE OF THE COUNTY ROAD LEADING FROM SAN CARLOS TO REDWOOD CITY, DISTANT THEREON SOUTH 42° 22' 30" EAST 913.16 FEET FROM THE

MOST WESTERLY CORNER OF THAT TRACT OF LAND KNOWN AS SPEEDWAY ACRES CONVEYED TO ASA E. HULL FROM C. B. MORTON, ET AL., BY DEED DATED JUNE 16, 1924 AND RECORDED IN BOOK 128 AT PAGE 107 (23249A), OFFICIAL RECORDS OF SAN MATEO COUNTY; THENCE FROM SAID POINT OF BEGINNING LEAVING THE NORTHEASTERLY LINE OF SAID COUNTY ROAD, NORTH 48° 43' EAST 234.56 FEET TO THE SOUTHWESTERLY LINE OF THE LAND DESCRIBED AS PARCEL 2 IN THE DEED TO SOUTHERN PACIFIC RAILROAD COMPANY RECORDED JUNE 18, 1926 IN BOOK 243 AT PAGE 17 (62690A), OFFICIAL RECORDS OF SAN MATEO COUNTY THENCE ALONG THE LAST MENTIONED LINE, SOUTH 42° 22' 30" EAST 56.68 FEET TO THE NORTHWESTERLY LINE OF COMMERCIAL WAY AS

ESTABLISHED BY DEED TO THE CITY OF SAN CARLOS, A MUNICIPAL CORPORATION, RECORDED OCTOBER 12, 1973 IN BOOK 6485 AT PAGE 501 (82827AG) OFFICIAL RECORDS OF SAN MATEO

COUNTY THENCE ALONG SAID NORTHWESTERLY LINE OF COMMERCIAL WAY AND THE SOUTHWESTERLY PROLONGATION THEREOF, SOUTH 48° 53' WEST 234.56 FEET TO THE

NORTHEASTERLY LINE OF SAID COUNTY ROAD THENCE ALONG THE LAST MENTIONED LINE, NORTH 42° 12' 30" WEST 56.68 FEET TO THE POINT OF BEGINNING.

PARCEL THREE:

BEING ALL OF PARCEL 2 AS DESCRIBED IN THE DEED FROM CALIFORNIA CONCRETE PRODUCTS AND ASA E. HULL TO SOUTHERN PACIFIC RAILROAD COMPANY RECORDED JUNE 18, 1926 IN VOLUME 243 OF OFFICIAL RECORDS AT PAGE 17 (243 O.R. 17); AND A PORTION OF PARCEL 2 AS DESCRIBED IN THE DEED FROM K.A. WINTER ET. AL. TO SOUTHERN PACIFIC RAILROAD COMPANY RECORDED JUNE 18, 1926 IN VOLUME 243 OF OFFICIAL RECORDS AT PAGE 12 (243 O.R. 12); BEING MORE PARTICULARLY DESCRIBED AS FOLLOWS:

BEGINNING AT THE MOST SOUTHERLY CORNER OF SAID PARCEL 2 OF SAID 243 O.R. 17; THENCE ALONG THE SOUTHWESTERLY LINE OF SAID PARCEL NORTH 42°22'30" WEST 293.10 FEET TO THE MOST SOUTHERLY CORNER OF SAID PARCEL 2 OF SAID 243 O.R. 12; THENCE ALONG THE SOUTHWESTERLY LINE OF SAID PARCEL NORTH 42°22'30" WEST 56.70 FEET TO

7.f
October 23, 2023 Packet Pg. 182
Order Number: NCS-1033730-SC
Page Number: 10
First American Title Insurance Company
THE BEGINNING OF A TANGENT CURVE TO THE LEFT HAVING A RADIUS OF 397.97 FEET; THENCE NORTHWESTERLY ALONG SAID CURVE THROUGH A CENTRAL ANGLE OF 1°29'08" A DISTANCE OF 10.32 FEET TO THE SOUTHEASTERLY LINE OF THE LANDS AS DESCRIBED IN THE QUITCLAIM DEED FROM UNION PACIFIC RAILROAD COMPANY TO KELLOGG ET. AL. RECORDED MAY 31, 2002 IN DOCUMENT NUMBER 2002-106037, OFFICIAL RECORDS OF SAN MATEO COUNTY; THENCE ALONG SAID SOUTHEASTERLY LINE NORTH 48°53'00" EAST 17.01 FEET TO A POINT ON THE NORTHEASTERLY LINE OF SAID PARCEL 2 OF SAID 243 O.R. 12; SAID POINT LYING A CURVE CONCAVE TO THE SOUTHWEST HAVING A RADIUS OF 414.97 FEET; A RADIAL LINE TO SAID POINT BEARING NORTH 46°15'05" EAST;
THENCE SOUTHEASTERLY ALONG SAID CURVE THROUGH A CENTRAL ANGLE OF 1°22'25" A DISTANCE OF 9.95 FEET;
THENCE TANGENT FROM SAID CURVE ALONG SAID NORTHEASTERLY LINE SOUTH 42°22'30" EAST

57.07 FEET TO THE MOST NORTHERLY CORNER OF SAID PARCEL 2 OF SAID 243 O.R. 17; THENCE ALONG THE NORTHEASTERLY LINE OF SAID PARCEL SOUTH 42°22'30" EAST 293.10 FEET TO THE SOUTHEASTERLY CORNER OF SAID PARCEL;
THENCE ALONG THE SOUTHEASTERLY LINE OF SAID PARCEL SOUTH 48°53'00" WEST 17.00 FEET TO THE POINT OF BEGINNING.

EXCEPTING THEREFROM ALL MINERALS AND ALL MINERAL RIGHTS OF EVERY KIND AND CHARACTER

NOW KNOWN TO EXIST OR HEREAFTER DISCOVERED UNDERLYING THE PROPERTY, INCLUDING,

WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, OIL AND GAS AND RIGHTS THERETO,

TOGETHER WITH THE SOLE, EXCLUSIVE AND PERPETUAL RIGHT TO EXPLORE FOR, REMOVE AND

DISPOSE OF SAID MINERALS BY ANY MEANS OR METHODS SUITABLE TO GRANTOR, ITS SUCCESSORS

AND ASSIGNS, BUT WITHOUT ENTERING UPON OR USING THE SURFACE OF THE PROPERTY, AND IN

SUCH MANNER AS NOT TO DAMAGE THE SURFACE OF THE PROPERTY, OR TO INTERFERE WITH THE

USE THEREOF BY GRANTEE, HER HEIRS AND ASSIGNS, AS RESERVED IN QUITCLAIM DEED RECORDED OCTOBER 26, 2007 AS INSTRUMENT NO. 2007-154663 OF OFFICIAL RECORDS.

PARCEL FOUR:

BEGINNING AT THE MOST SOUTHERLY CORNER OF THAT CERTAIN 20 ACRE TRACT DESCRIBED IN THE AGREEMENT BETWEEN ASA B. HULL AND I.H. WINTER ET AL, RECORDED NOVEMBER 24, 1925 IN BOOK 201 OF OFFICIAL RECORDS OF SAN MATEO COUNTY AT PAGE 290; THENCE FROM SAID POINT OF BEGINNING ALONG THE SOUTHEASTERLY LINE OF SAID 20 ACRE TRACT, NORTH 48°53' EAST 230.00 FEET; THENCE LEAVING SAID SOUTHEASTERLY LINE AND RUNNING ACROSS SAID 20 ACRE TRACT, NORTH 42° 22' 30" WEST 90.02 FEET AND SOUTH 48° 53' WEST 230.00 FEET TO A POINT ON THE NORTHEASTERLY LINE OF THE COUNTY ROAD LEADING FROM REDWOOD CITY TO CARLOS; THENCE ALONG SAID NORTHEASTERLY LINE OF SAID COUNTY ROAD, SOUTH 42° 22' 30" EAST 90.03 FEET TO THE POINT OF BEGINNING.

PARCEL FIVE:

BEGINNING AT A POINT ON THE NORTHEASTERLY LINE OF THAT CERTAIN COUNTY ROAD LEADING

FROM REDWOOD CITY TO SAN CARLOS, SAID POINT OF BEGINNING BEING DISTANT ALONG SAID NORTHEASTERLY LINE OF SAID COUNTY ROAD NORTH 42° 22’ 30” WEST 180.04 FEET FROM THE MOST SOUTHERLY CORNER OF THAT CERTAIN 20 ACRE TRACT DESCRIBED IN AGREEMENT BETWEEN ASA E. HULL AND K.A. WINTER, ET AL, SAID AGREEMENT BEING FILED FOR RECORD NOVEMBER 24, 1925 IN VOLUME 201 OF OFFICIAL RECORDS AT PAGE 290, RECORDS OF SAN MATEO COUNTY, CALIFORNIA; THENCE FROM SAID POINT OF BEGINNING ALONG SAID NORTHEASTERLY LINE OF SAID

7.f
October 23, 2023 Packet Pg. 183
Order Number: NCS-1033730-SC
Page Number: 11
First American Title Insurance Company
COUNTY ROAD NORTH 42° 22’ 30” WEST 90.02 FEET TO A POINT WHERE SAID NORTHEASTERLY LINE OF SAID COUNTY ROAD IS INTERSECTED BY THE SOUTHEASTERLY LINE OF A 50 FOOT PRIVATE ROAD RUNNING THROUGH ABOVE DESCRIBED 20 ACRE TRACT; THENCE ALONG SAID SOUTHEASTERLY LINE OF SAID 50 FOOT ROAD NORTH 48° 53’ EAST 230 FEET; THENCE LEAVING SAID SOUTHEASTERLY LINE OF SAID 50 FOOT PRIVATE ROAD AND RUNNING SOUTH 42° 22’ 30” EAST 90.02 FEET AND SOUTH 48° 53’ WEST 230.0 FEET TO THE POINT OF BEGINNING.

PARCEL SIX:

BEGINNING AT A POINT ON THE NORTHEASTERLY LINE OF THE OLD COUNTY ROAD FROM REDWOOD

CITY TO SAN CARLOS (SAID ROAD LYING NORTHEASTERLY OF THE TRACKS OF THE SOUTHERN

PACIFIC RAILROAD), SAID POINT OF BEGINNING BEING DISTANT ALONG SAID NORTHEASTERLY LINE OF SAID ROAD, NORTH 42° 22’ 30” WEST 90.02 FEET FROM THE MOST SOUTHERLY CORNER OF THAT CERTAIN 20 ACRE TRACT DESCRIBED IN AGREEMENT BETWEEN ASA E. HULL AND K.A. WINTER, ET AL, RECORDED NOVEMBER 24, 1925 IN VOLUME 201 OF OFFICIAL RECORDS AT PAGE 290, RECORDS OF SAN MATEO COUNTY, CALIFORNIA; THENCE FROM SAID POINT OF BEGINNING ALONG SAID NORTHEASTERLY LINE OF SAID COUNTY ROAD, NORTH 42°22’ 30” WEST 90.02 FEET; THENCE NORTH 48° 53’ EAST 230.0 FEET; THENCE SOUTH 42°22’ 30” EAST 90.02 FEET; THENCE SOUTH 48°53’ WEST 230.0 FEET TO THE POINT OF BEGINNING.

PARCEL SEVEN:

A PARCEL OF LAND SITUATE IN THE CITY OF SAN CARLOS, COUNTY OF SAN MATEO, STATE OF CALIFORNIA, BEING PARCEL THREE AS DESCRIBED IN A DEED RECORDED NOVEMBER 26, 1991 IN DOCUMENT NUMBER 91155625 OFFICIAL RECORDS OF SAN MATEO COUNTY, MORE PARTICULARLY DESCRIBED AS FOLLOWS:

BEGINNING AT A POINT ON THE SOUTHEASTERLY LINE OF THAT CERTAIN 20 ACRES TRACT DESCRIBED IN THE AGREEMENT BETWEEN ASA E. HULL AND K.A. WINTER, ET AL, RECORDED NOVEMBER 24, 1925 IN BOOK 201 OFFICIAL RECORDS OF SAN MATEO COUNTY, PAGE 290, SAID POINT OF BEGINNING BEING DISTANT ALONG SAID SOUTHEASTERLY LINE NORTH 48° 53’ EAST 230.0 FEET FROM THE MOST SOUTHERLY CORNER OF SAID 20 ACRE TRACT; THENCE FROM SAID POINT OF BEGINNING ALONG SAID SOUTHEASTERLY LINE NORTH 48° 53’ EAST, 100.00 FEET, THENCE LEAVING SAID SOUTHEASTERLY LINE AND RUNNING ACROSS SAID 20 ACRE TRACT NORTH 41° 07’ WEST, 270.00 FEET OF THE SOUTHEASTERLY LINE OF A 50 FOOT PRIVATE ROAD RUNNING THROUGH THE ABOVE DESCRIBED 20 ACRE TRACT; THENCE ALONG SAID SOUTHEASTERLY LINE OF SAID 50 FOOT PRIVATE ROAD SOUTH 48° 53’ WEST, 105.93 FEET; THENCE LEAVING SAID SOUTHEASTERLY LINE OF SAID 50 FOOT ROAD SOUTH 42° 22’ 30” EAST, 270.06 FEET TO THE POINT OF BEGINNING.

EXCEPTING THEREFROM THAT PORTION OF THE ABOVE DESCRIBED PROPERTY WHICH LIES SOUTHEASTERLY OF A LINE PARALLEL TO AND 90.02 FEET MEASURED PERPENDICULARLY NORTHWESTERLY OF THE ABOVE SAID SOUTHEASTERLY LINE OF SAID 20 ACRE TRACT AND NORTHEASTERLY OF THE COURSE CALLED SOUTH 42° 22’ 30” EAST, 57.074 FEET AND THE NORTHWESTERLY EXTENSION THEREOF, AS SAID COURSE IS DESCRIBED IN PARCEL #2 OF THE ABOVE SAID DEED RECORDED JUNE 18, 1926 IN BOOK 243 OFFICIAL RECORDS OF SAN MATEO COUNTY PAGE 12.

ALSO EXCEPTING THEREFROM, THAT PORTION THEREOF LYING WITHIN THE PARCEL DESCRIBED IN

THE QUITCLAIM DEED FROM UNION PACIFIC RAILROAD COMPANY, A DELAWARE CORPORATION TO WANDA MAE ADAMS RECORDED OCTOBER 26, 2007 AS INSTRUMENT NO. 2007-154663 OF OFFICIAL RECORDS.

For reference purposes only:

7.f
October 23, 2023 Packet Pg. 184
Order Number: NCS-1033730-SC
Page Number: 12
First American Title Insurance Company
APN: 046-182-100 (affects Parcel One);
046-182-110 (affects Parcel Two);
046-182-150 (affects Parcel Three);
046-135-030 (affects Parcel Four);
046-135-010 (affects Parcel Five);
046-135-020 (affects Parcel Six);
046-135-040 (affects portion of Parcel Seven);
046-134-050 (affects portion of Parcel Seven);
046-134-060 (affects portion of Parcel Seven);
and 046-133-160 (affects portion of Parcel Seven)
JPN:
046-018-182-04A
046-018-182-05A
046-013-135-03A
046-013-135-01A
046-013-135-02A
046-013-134-03A
046-013-133-016A

7.f
October 23, 2023 Packet Pg. 185
71 EXHIBIT G

PARKING DIAGRAM

7.f
October 23, 2023 Packet Pg. 186
C
O
M
M
E
R
C

AI L ST
B
RA
N
S
T
E
N
R
D

OLD COUNTY ROAD
SOUTH
PHASE
NORTH
PHASE
(7) PUBLIC PARKING STALLS
(1) EV AMBULATORY STALL
(1) STANDARD EV STALL

EV STALL

PUBLIC PARKING STALL

BUILDING ENTRANCE
LEGEND
N
C O P Y R I G H T © 2 0 2 3 b y S T U D I O S a r c h i t e c t u r e Scale: 1" = 80'-0"

SURFACE PARKING DIAGRAM
841 OLD COUNTY RD
10/13/23

7.f
October 23, 2023 Packet Pg. 187
15 4.3 Taxes and Assessments. As of the Effective Date, assessments are in effect and applicable to the Property or the Project as shown on the latest property tax bill for the Property. City is not aware of any pending efforts to initiate or consider new or increased assessments that would apply to the Property or the Project. City may impose and Developer agrees to pay any and all existing, new, modified or increased taxes and assessments, other than Impact Fees, imposed on the Property or the Project in accordance with the laws in effect as of the date due, at the rate in effect at the time of payment. Nothing herein shall be construed so as to limit Developer from exercising whatever rights it may otherwise have in connection with protesting or otherwise objecting to the imposition of taxes or assessments on the Property; provided, Developer acknowledges being aware of all taxes and assessments in effect as of the Effective Date, and Developer accepts and agrees that it shall not protest or challenge their imposition on the Property and the Project. In the event an assessment district is lawfully formed to provide funding for services, improvements, maintenance or facilities which are substantially the same as those services, improvements, maintenance or facilities being funded by the fees or assessments to be paid by Developer under the Project Approvals or this Agreement, then at City’s election, taking into consideration City’s expectations as to when it would receive Developer’s payment of such fees or assessments, either (a) the fees or assessments to be paid by Developer shall be subject to reduction/credit in an amount equal to Developer’s new or increased assessment under the assessment district, or (b) the new assessment district shall reduce/credit Developer’s new assessment in an amount equal to such fees or assessments to be paid by Developer under the Project Approvals or this Agreement.

ARTICLE 5

DEVELOPER COMMUNITY BENEFITS COMMITMENTS

5.1 Public Benefits. Developer shall perform and provide the public benefit obligations described in this Section 5.1 in consideration for the rights and benefits conferred by City to Developer under this Agreement, which exceed those dedications, conditions, and exactions that may be imposed under Applicable Law.

5.1.1 POPA Easement. Prior to the issuance of final Certificate of Occupancy for the Project, Developer shall execute and record an easement and maintenance agreement providing for public access to both (1) the approximately 5,000 square foot portion of the central outdoor plaza located between the gate and Old County Road (“Front Plaza”) and (2) the approximately 12,000 square foot amenity courtyard between the buildings (“Courtyard”), each as shown in the Project Approvals and maintenance of the Front Plaza and Courtyard by Developer, in substantially the form attached hereto as Exhibit D (“POPA Easement”). The POPA Easement shall require Developer to allow public access to the Courtyard during daylight hours (sunrise to sundown) and to the Front Plaza during the longer of daylight hours (sunrise to sundown) or the hours that the tenant of the Community Benefit Space is open to the public, subject to the Developer’s reasonable rules and regulations related to safety, maintenance, and repairs, as well as improvements/renovations that meet the spirit and intent of the POPA Easement and subject to the reasonable approval of the Community Development Director.

7.f
October 23, 2023 Packet Pg. 188
16 The POPA Easement shall allow Developer to temporarily exclude the public or temporarily limit public access to portions of the Front Plaza and/or Courtyard if necessary to address safety concerns and perform maintenance and repairs to improvements within or immediately adjacent to the Front Plaza and to allow a reasonable limited number of private events per year for tenants of the Project and for non-profit or community events. The POPA Easement shall require Developer to maintain the Front Plaza and Courtyard at all times and indemnify and hold City harmless from any and all Claims arising from or relating to the design, construction, or maintenance of the Front Plaza and the public’s use thereof. The POPA Easement shall terminate in the event that (i) the Project is demolished or (ii) the Project undergoes a substantial change that is not already permitted under the Project Approvals and public access cannot be maintained by modifying the boundaries of the Front Plaza and Courtyard, provided that the POPA Easement shall not terminate in the event of demolition and reconstruction of any building or buildings in the Project following a casualty.

5.1.2 Recycled Water Pipe. At the time of issuance of a certificate of occupancy, the water infrastructure for the Project shall include dual plumbing for potable and recycled water, with separate pipe lines composed of appropriate material to accommodate recycled water.

5.2 Community Benefits.

5.2.1 Developer shall design and construct the improvements for the Project listed below and pay the following amounts listed below (“Community Benefits”) in exchange for the approval of the Planned Development zoning designation and a Planned Development Plan that allow Developer to construct buildings with a greater height and Floor Area Ratio than permitted under the Property’s previous Heavy Industrial zoning designation. These approvals have a value of Fourteen Million Dollars ($14,000,000). The Parties agree that the Community Benefits have a value of Seven Million Six Hundred Ninety Thousand Dollars ($7,690,000). (a) Design and construction of a space to be occupied by a Restaurant/Coffee Shop (or other Community Benefit Use pursuant to Section 5.2.4 below), along with four (4) designated parking spaces for customers (not employees) in the surface parking lot during occupancy (“Exclusive Retail Customer Spaces”) in the location shown in the Project Approvals:
 Approximately 1,500 square feet
 Value: $555,000
(b) Design and construction of a Bike/Pedestrian Path as shown in the Project Approvals:
 Approximately 4,240 square feet
 Value: $148,400

7.f
October 23, 2023 Packet Pg. 189
17 (c) Provide public parking on nights and , weekends , and federal holidays on the surface parking lot.
 Approximately 46 parking spaces, subject to the Exclusive Retail Customer Spaces
 Value: $690,000
(d) Addition of one dual head electric vehicle charging hub to provide two (2) charging stations on the surface parking lot.
(e) Designate seven (7) parking spaces for use by persons visiting the Community Benefit Space (defined below), Front Plaza, and/or Courtyard during the hours that any of the Community Benefit Space (defined below), Front Plaza, and/or Courtyard are open to the public, in addition to the times described in (c).
(e)(f) Payments:
 Green Energy Efficiency & Sustainability Fund- $500,000  Community Improvement & Recreation Fund - $3,000,000
 Downtown Improvements Fund - $2,796,000

5.2.2 Design and Construction of Community Benefit Space and Bike/Pedestrian Path.

The Community Benefit Space (defined in Section 5.2.4) and Bike/Pedestrian Path referenced in Section 5.2.1 shall be designed and submitted for approval as part of the Project building permit application, and shall be constructed in substantial conformance with the Project Approvals. The Parties shall enter into a Subdivision Improvement Agreement with respect to the Bike/Pedestrian Path and any work related to the Bike/Pedestrian Path that occurs on public property will be a public work subject to Prevailing Wage Laws.

5.2.3 Timing of Payments. The payments set forth in Section 5.2.1(c) shall be made in full prior to the issuance of the first building permit for the Project.

5.2.4 Community Benefit Space Timing. The South Phase building shown in the Project Approvals (“South Building”) shall include space suitable for a Restaurant/Coffee Shop Use or Community Benefit Use (“Community Benefit Space”). The final certificate of occupancy for the South Building must be requested (except as provided in this Section 5.2.4) and issued prior to the issuance of a final certificate of occupancy for any other building or structure in the Project. In the event that Developer has commenced construction of the South Building and a final certificate of occupancy for any other building or structure is requested by the Developer, the Developer will deposit $555,000 with the City which shall be returned in full without interest to the Developer upon issuance of the final certificate of occupancy for the South Building that includes the Community Benefit Space in compliance with this Agreement. In the event that the South Building has commenced construction under this Section, but does not receive its final certificate of

7.f
October 23, 2023 Packet Pg. 190
19 Developer shall also provide one dual head electric vehicle charging hub to create two (2) charging stations and designate two (2) parking spaces in the surface parking lot for vehicles using the charging stations. The charging stations shall be available for use by the public during the same hours as the other spaces in the surface parking lot. The public parking spaces available nights and the weekends, the seven (7) parking spaces available for use by visitors of the Front Plaza, Courtyard, or Community Benefit Space, and the two (2) parking spaces with charging stations shall be in substantially the locations shown on the conceputal conceptual plan attached hereto as Exhibit G.

ARTICLE 6

ANNUAL REVIEW

6.1 Periodic Review.

6.1.1 As required by the City of San Carlos City Code Section 18.37.080, Developer shall be required to demonstrate compliance with the provisions of the Agreement at least once a year at which time the Community Development Director shall review the Agreement.

6.1.2 The annual review shall be conducted as provided herein:
(a) Documentation of Compliance. By the last business day of January of each year, the Developer shall provide documentation of its compliance with the Agreement during the previous calendar year. Promptly upon receipt of Developer’s documentation of compliance, the City’s Community Development Director shall review the documentation and determine, on the basis of substantial evidence, whether the Developer has complied with the provisions of this Agreement.
(b) Finding of Compliance. If the Community Development Director, on the basis of substantial evidence, finds compliance by Developer with the provisions of this Agreement, the Community Development Director shall issue a finding of compliance, which shall be in recordable form and may be recorded with the County Recorder after conclusion of the review. (c) Finding of Noncompliance. If the Community Development Director finds Developer has not complied with the provisions of this Agreement, the Community Development Director may issue a finding of noncompliance which may be recorded by the City with the County Recorder after it becomes final. The Community Development Director shall specify in writing to Developer the respects in which applicant has failed to comply, and shall set forth terms of compliance and specify a reasonable time for Developer to meet the terms of compliance.

7.f
October 23, 2023 Packet Pg. 191
46 HVAC
HVAC
- HVAC duct chase distribution into space based on
standard retail use. All distribution within space by
tenant. Any extraordinary requirements necessitated
because of Tenant’s use of the Premises will be at the
expense of Tenant. Roof top space provided for
tenant’s equipment
Electrical Signs
- One (1) J-box for signage located at the main entrance lo space.

Tenant is responsible for all connections, equipment
and devices as required by Tenant design or local
jurisdiction codes, including exit signs.

Medium-Voltage Electrical
Distribution
- Electrical service provided at main electrical room to be 400 Amps (120/208V, 3-phase, 4-wire)
Distribution to space by tenant
- Lighting and exit signs for the space including new
restroom that meet the local jurisdiction codes.

Communications
Tenant will be required upon the “Delivery of the
Premises” to switch all utility account(s) responsibility and all billing information into their name.

Telephone System
- 2” telephone/data conduit to space with pull string.
- Tenant is responsible for all connections, equipment
and devices as required by Tenant design or local
jurisdiction codes and for provisioning telephone and
data service.

Water Utility
- Landlord to provide the water submeter (including
capacity charges) with a 5/8" restricted submeter size.

Any upsizing of the submeter is the responsibility of
the Tenant (in no event shall exceed a 1” submeter)
and shall be reimbursed to the Landlord.
- Tenant is responsible for activation of the water
submeter account with the local utility.
- Tenant is responsible for all plumbing distribution and equipment.

Electric Meter
- LL provided meter socket.
- Tenant is responsible for activation their account in their name with the local utility company.

Parking
Spaces
- LL will designate four (4) parking spaces on the surface parking lot for the exclusive customer use during Tenant’s business hours. Tenant and Tenant employees may not use these spaces.

7.f
October 23, 2023 Packet Pg. 192
51 4. Default and Remedies. Breach of, failure, or delay by Owner to perform any term or condition of this POPA Agreement shall constitute a default. In the event of any default of any term, condition, or obligation of this POPA Agreement, City shall give the Owner notice in writing specifying the nature of the alleged default and the manner in which such default may be satisfactorily cured (“Notice of Breach”). The defaulting party shall cure the default within 30 days following receipt of the Notice of Breach, provided, however, if the nature of the alleged default is non-monetary and such that it cannot reasonably be cured within such 30-day period, then the commencement of the cure within such time period, and the diligent prosecution to completion of the cure thereafter, shall be deemed to be a cure, provided that if the cure is not diligently prosecuted to completion, then no additional cure period shall be provided. If the alleged failure is cured within the time provided above, then no default shall exist and the City shall take no further action to exercise any remedies available hereunder. If the alleged failure is not cured, then a default shall exist under this POPA Agreement and the City may bring any action at law or in equity to enforce the terms of this POPA Agreement. In addition, if the default is the failure to meet the Maintenance Standards set forth in Section 3 above, the City, in addition to its other rights and remedies, may enter and perform or cause its agents and contractors to enter the Easement Areas and perform the required maintenance and City costs shall be reimbursed by Owner within thirty (30) days of billing by City or City may record a lien or place the amount owed as a special assessment against the Property in the amount of the work performed.

5. Temporary Closure for Maintenance and Events. Owner reserves the right to temporarily exclude the public from or limit public access to all or portions of the Easement Areas if necessary to address safety concerns and perform maintenance and repairs to improvements within or immediately adjacent to the Front Plaza. In addition, the Owner reserves the right to exclude the public from all or portions of the Easement Areas a reasonable limited number of times per year for events or exclusive use of the Easement Areas by tenants of the Project (each individually a “Tenant Event” and collectively, “Tenant Events”), not to exceed four (4) Tenant Events per year for the Front Plaza Easement Area, and not to exceed two (2) times per month for the Courtyard Easement Area. Each such Tenant Event may not last more than 24 hours (although two Tenant Events could allow a total of 48 hours), including any set up or tear down/clean-up activities. In addition to the Tenant Events, non-profit or non-profits or other not-for-profit community organizations with principal offices within the City limits (“Community Groups”) may hold private events on the Front Plaza Easement Area and/or Courtyard Easement Area up to six (6) times per year (each no more than 24 hours per event including set up/clean up) under a typical form of event agreement (i.e. event details, cleaning fee, insurance and liability protection for the Owner, organization and City). Prior to the opening of the Front Plaza and Courtyard to tenants and the public, Developer shall designate an individual to whom Community Groups may make reservation requests or develop an electronic system for submission of reservation requests. The Developer shall require tenants to contact the same person or use the same electronic system for Tenant Events reservation requests. Reservation requests shall not be unreasonably withheld, conditioned, each to be approved by the Owner, Tenant and City Community Development Directoror delayed. During events held by non-profit or community organizations, event attendees and event volunteers and staff shall be permitted to park in the surface parking lot at no charge. In the event of planned maintenance or a Tenant Event during which the Front Plaza Easement Area and/or Courtyard Easement Area will be closed, Owner shall post signs within the Front Plaza Easement Area and/or Courtyard Easement Area at least forty-eight (48) hours prior to the closure for a Tenant Event or for planned maintenance. In the case of an emergency or repairs requiring

7.f
October 23, 2023 Packet Pg. 193
57 WHEREAS, the Development Agreement requires Owner and City to execute a parking agreement under which Owner will share the Project’s commercial parking with the public by offering nightly and weekend public parking in the surface parking lot.

WHEREAS, the Parties desire to execute and record this Agreement to make the Project’s commercial parking available to the public upon the terms and conditions stated below to satisfy the requirements of the Development Agreement.

NOW, THEREFORE, in consideration of the foregoing and for other good and valuable consideration, the receipt and adequacy of which are acknowledged, the Parties hereby agree as follows:

1. Parking Terms and Conditions.

1.1. Public Use of Surface Parking. The surface parking lot, together with those areas necessary for ingress and egress to the surface parking lot as more particularly described in Exhibit B (collectively, the “Public Parking Area”), shall be available for use by the general public during the Hours of Public Use (as said term is defined below). The Public Parking Area shall include one dual head electric vehicle charging hub to provide two (2) charging stations and Owner shall designate two (2) parking spaces for vehicles using the charging stations. Owner may modify the Public Parking Area from time to time, in its sole discretion, upon providing reasonable advance notice to City of such modifications, provided however, that nothing herein limits the Owner’s obligation to comply with the requirements to obtain building permits, and/or City approval in its regulatory capacity of the modifications, if applicable. Owner shall designate seven (7) spaces within the Public Parking Area (“Plaza Public Parking Spaces”) to be available for use by members of the public visiting the Front Plaza, Courtyard, or the retail tenant during (i) the hours that any of the publicly accessible open spaces or the retail tenant are open to the public and (ii) the Hours of Public Use. The Plaza Public Parking Spaces shall be marked with conspicuous signage.

1.2. Hours of Public Use. The Public Parking Area shall be open to the general public Monday through Friday from 6:00 p.m. to 11:00 p.m.; and Saturday, Sunday, and Federal holidays from 7:00 a.m. sunrise to 11:00 p.m. and during such other hours that Owner and City have agreed to grant a non-profit or community organization the right to hold an event in the courtyard in the Project pursuant to the POPA Agreement (collectively the “Hours of Public Use”). At all other times, Owner shall have exclusive control over the Public Parking Area for the exclusive use of the Owner, Owner’s tenants, and the guests, licensees, employees, agents, servants and representatives of Owner and Owner’s tenants.

Owner shall post multiple conspicuous signs, as approved by the City, in the Public Parking Area to inform the public of the Hours of Public Use.

1.3. Parking Rates. Owner shall make the Public Parking Area available at no cost to the public. Owner shall be free to establish parking rates for the other parking areas in the Project in its sole and absolute discretion, and Owner shall have the right to install

7.f
October 23, 2023 Packet Pg. 194

CITY COUNCIL

STAFF REPORT
MEETING DATE: October 23, 2023
ITEM TITLE: Consideration of Introducing an Ordinance Amending San Carlos Municipal Code Title 18 - Zoning to Create Objective Design Standards for Single-Family Development.

RECOMMENDATION:

The Planning and Transportation Commission (PTC) recommends that the City Council introduce an Ordinance to create objective design standards for single-family development by amending the San Carlos Municipal Code Title 18 - Zoning: Chapter 18.03 - Rules of Measurement; 18.04 - Residential Districts; 18.12 - Hillside Overlay District; 18.15 - General Site Regulations; 18.20 - Parking and Loading, 18.26 - Planning Authorities; 18.27 - Common Procedures; 18.29 - Design Review; 18.40 - Use Classification; and 18.41 - Terms and Definitions; and adding a new Subsection: 18.23.310 - Urban Infill Units, Under 18.23 - Standards for Specific Uses and Activities.

FISCAL IMPLICATIONS:

There is no fiscal impact, and no additional appropriation is needed at this time.

This initiative is being managed by Community Development Department staff with consulting support from MIG. The City Council allocated the funds for MIG’s consulting services in February 2022, for an amount not to exceed $305,095. MIG’s services include developing objective design standards for residential development, including single-family development and mixed-use/ multifamily development.

SUMMARY:

Establishing objective design standards for residential development is essential to ensure orderly and streamlined development, compliance with state law requirements, and to meet the 2023- 2031 Regional Housing Needs Allocation (RHNA) of 2,735 new housing units.

Currently, the City utilizes a combination of objective and subjective design standards to review single-family development projects. The process involves City staff, the Residential Design Review Committee (RDRC), the PTC, and occasionally, the City Council. City staff has received feedback that this process is time consuming, expensive, and burdensome for applicants.

If the proposed zoning amendments are adopted, single-family development projects would be required to comply with objective design standards for single-family development, as set forth in Title 18 of the San Carlos Municipal Code and applicable state law.

8.a
October 23, 2023 Packet Pg. 195
BACKGROUND:

Why is the City Developing Objective Design Standards?
On January 23, 2023, the City Council adopted the 2023-2031 Housing Element as a part of the Focused General Plan Update. The updated Housing Element aims to accommodate additional residential units and remove obstacles to creating housing. Action HOU 4.4 identifies the need for the creation and adoption of objective design standards for residential development. This also aligns with new state law that requires cities to create objective design standards that apply to projects with two or more residential units.

In 2021, the City Council directed staff to prepare objective design standards for all residential development, including single-family homes, in order to:
• Comply with state law.
• Implement policies of the San Carlos 2030 General Plan and Housing Element and help meet the Regional Housing Needs Allocation (RHNA).
• Prevent additional governmental constraints on the production of housing. • Create standards that are verifiable and measurable.
• Streamline project review and permitting.
• Ensure consistent application of standards for single-family homes, with and without accessory dwelling units (ADUs).

Staff anticipates future state legislation may require objective design standards for all types of housing projects including single-unit development. Thus, having these standards in effect prior to the passage of any such law would benefit the City.

Objective Design Standards Process
City staff divided the objective design standards development process into two phases. • Phase 1: Objective Design Standards for Single-Family Development. From March 2022 to August 2023, City staff and the consultant team focused only on the creation of objective design standards for single-family development. “Single-family development” includes single-family homes, junior accessory dwelling units (JADUs), ADUs, attached or detached duplexes, and urban infill units (also known as SB-9 units). These standards are before the Council for consideration this evening.
• Phase 2: Objective Design Standards for Mixed-Use and Multi-Family Development.

The objective design standards for mixed-use and multifamily developments will establish clear criteria for landscaping, transitional guidelines, massing, and articulation. This will streamline the project review process for multi-family and mixed-use development and potentially accelerate the creation of housing units. Staff anticipates presenting the draft standards to the City Council in early 2024.

8.a
October 23, 2023 Packet Pg. 196
Planning and Transportation Commission Recommendation
On June 19, 2023, City staff and the consultant team presented the draft objective design standards for single-family development to the PTC.1 The PTC passed a Resolution recommending that the City Council adopt the proposed objective design standards, with three recommendations. Please refer to Attachment 2 for the Resolution adopted by the PTC.

The PTC’s recommendations regarded: 1) zero lot line development, 2) flag lots for urban infill units, and 3) compliance review procedures. Additional details are provided below.

1. Zero Lot Line Development: The PTC recommended that staff investigate the feasibility of allowing zero lot line development, meaning allowing development at the lot line with no setbacks, for small lot subdivision projects and urban infill units (SB-9 Units) subdivisions. The consultant team conducted an analysis of the considerations for allowing zero lot line development (see Attachment 5).

Staff Recommendation: Further study is needed. The introduction of zero lot lines would significantly impact the overall fabric and configuration of buildings in San Carlos and is a major policy decision. Therefore, staff believes it is crucial to research this further before presenting a policy recommendation to the City Council.

Should the City Council choose to move forward with the PTC’s recommendation regarding zero lot lines, the Council may direct staff to reintroduce the proposal as a future initiative.

2. Flag Lots for Urban Infill Units: The PTC recommended that staff explore the feasibility of allowing flag lots throughout San Carlos to accommodate additional urban infill units (SB-9 units). A “flag lot” allows access to the street via a narrow driveway, or “flag pole” (see Figure 1).

Figure 1: Example of a Flag Lot
Staff Recommendation: Further study is needed. Staff acknowledges that permitting flag lots throughout San Carlos could potentially create more opportunities for urban infill 1 The staff report, meeting video, and meeting minutes for the June 19, 2023 PTC can be found here:
https://cityofsancarlos.primegov.com/Portal/Meeting?meetingTemplateId=13215

8.a
October 23, 2023 Packet Pg. 197
units. However, such a decision could also bring about significant changes to the overall city development patterns. Presently, flag lots are only allowed for specific exceptional cases as stipulated in the San Carlos Municipal Code Section 17.16.040. Internal discussion and consultation with other departments such as Public Works would be necessary to better understand any infrastructure implications. Therefore, staff believes that allowing flag lots by right would necessitate further research and analysis.

Should the City Council choose to study the PTC’s recommendation regarding flag lots, the Council may direct staff to reintroduce further research on citywide flag lots as an independent project in the coming year, complete with comprehensive research and analysis.

3. Compliance Review Procedures: The PTC recommended that staff provide additional details about the new compliance review process, which is intended to replace the RDRC process.

Staff Analysis: Additional details about the proposed compliance review process can be found in the “Analysis” section below.

ANALYSIS:

City staff and the consultant team have prepared draft objective design standards for single-family development for the City Council’s review and consideration. The draft Objective Design Standards are based on:
• Input received throughout the community engagement process (see Attachment 3, Community Outreach Summary and Meeting Minutes).
• knowledge of the unique design character and housing styles in San Carlos. • An understanding of what works well in creating objective design standards.

The objective design standards process has been guided by the following key principles:

1. Streamline the housing construction and review process while adhering to state law and underlying development standards.

2. Preserve the overall character of the neighborhoods by implementing good design principles in line with the "Objective Standards" guidelines mandated by the state law.

3. Prepare design standards that are clear, objective, and free from subjectivity for all singlefamily development use types.

The draft objective design standards for single-family development includes zoning amendments that span eleven chapters in the San Carlos Municipal Code. Table 1 provides an overview of the amendments in each chapter. For specific details, refer to Attachment 1 which shows the amendments in strikethrough format.

Table 1. Summary of Proposed Amendments

8.a
October 23, 2023 Packet Pg. 198
San Carlos Municipal Code Chapters Summary of Proposed Amendments 1 18.03 (Rules of Measurement) Clarifying the rule of overall height measurement. 2 18.04 (Residential Districts)
Making existing design standards objective, adding
objective design standards for duplexes, and
amending the use table.
3 18.12 (Hillside Overlay District)
Clarifying the “Natural State” requirement,
measuring height, and downhill facing façade step
back.
4 18.15 (General Site Regulations)
Allowing porches to be closer to the sidewalk by
amending the porch projection allowance
dimension.
5 18.20 (Parking and Loading) Modifying driveway parking requirement when proposing a one-car garage.
6 18.26 (Planning Authorities) Striking roles and responsibilities of the Residential Design Review Committee.
7 18.27 (Common Procedures) Amending roles and responsibilities. 8 18.29 (Design Review)
Details are below.

Removing RDRC review requirement, introducing a
new neighborhood notification process.
9 18.40 (Use Classification) Modifying use classifications for single-family development, adding Urban Infill Units use type.
10 18.41 (Terms and Definitions) Adding new definitions such as lower story wall, natural state, etc.
11 New Section: 18.23.310 (Standards of
Specific Uses)
Details are below.

Introducing a new section dedicated to Urban Infill
Units (SB-9 units).

If the City Council introduces the Ordinance as proposed, this would mean:
• All single-family development projects would be required to be consistent with the objective design standards;
• The current RDRC process would be substituted with the compliance review process; and
• Only single-family projects that necessitate deviation or exception from the objective design standards would be subject to discretionary design review procedures. This would include discretionary review by the PTC, as elaborated in Chapter 18.29.

Additional details are provided below.

Proposed Changes to SCMC Section 18.29 - Design Review
Currently, SCMC Section 18.29 - Design Review outlines the scope, threshold, review criteria, and required findings for single-family development requiring design review by the RDRC. As a part of the objective design standards, discretionary design review for single-family development by the RDRC is proposed to be discontinued.

8.a
October 23, 2023 Packet Pg. 199
This section provides more information about the current RDRC process and why the RDRC is proposed for discontinuation.

What projects are currently reviewed by the RDRC?
Currently, the RDRC reviews all projects that meet the following thresholds:
• All new homes.
• For lots less than 7,500 square feet, additions that create a total of 3,000 square feet of floor area or more.
• If a project results in the destruction and removal of fifty percent or more of the enclosing exterior walls.
• When the Community Development Director, in their opinion, determines that public interest would better be served by referral to the RDRC.

Staff-level review is conducted for any projects below these thresholds.

Time and Financial Costs of the Current RDRC Process
City staff received feedback that the RDRC process is time-consuming, expensive, and burdensome for applicants. Table 3 shows the time and financial costs of a staff-level review versus a RDRC-level review.

If adopted, the objective design standards for single-family development will provide more clarity to applicants and the community. The standards will also limit discretion when reviewing applications for single-family residential projects, potentially making the review process more efficient and less time consuming.

Table 3. Staff-Level Review versus RDRC Review
Who is the final reviewer? How long is the
typical review period?
What is the cost
to the applicant?2
City staff 100 days $3,143 (First floor addition)
$4,713 (Second floor addition)
Residential Design Review
Committee 200 days
$7,856 (First floor addition)
$10,999 (New construction, or
Second floor addition)
The RDRC is proposed to be discontinued for the following reasons:
• The state-required objective design standards prohibit discretion in evaluating design. The RDRC cannot require changes to design that meet the objective standards. • Maintaining the RDRC may give community members an inaccurate understanding of the changes that can be required by the City and the RDRC.
2 User Fees, FY 2023-2024. City of San Carlos website:
https://www.cityofsancarlos.org/city_hall/departments_and_divisions/administrative_services/finance/city_ fees_and_cost_of_services/index.php#outer-125

8.a
October 23, 2023 Packet Pg. 200
• The RDRC currently has limited ability to change projects, including changes that would reduce the size of the residence.
• Maintaining the RDRC will elongate the process for review and approval of single-family residential projects.
• Maintaining the RDRC will impose an unnecessary financial burden on applicants.

Proposed “Compliance Review” Process
If the RDRC is discontinued, then single-family development projects would be reviewed by staff under the new compliance review procedures.

For single-family projects that seek exceptions or deviations to the objective design standards, the PTC will conduct the discretionary design review. The PTC’s review will be based on the existing criteria and findings specified in Chapter 18.29 - Design Review of the San Carlos Municipal Code.

Proposed “Neighborhood Notification” Process
If the City Council supports discontinuation of the RDRC review process, a new neighborhood notification process for the compliance review would be implemented. This would be applicable to projects that meet the same thresholds that currently trigger RDRC review.

The neighborhood notification process would not be required for projects that are under these thresholds. The neighborhood notification process will involve the following steps:
• Step 1: Pre-Application Meeting/Mail Notification
Currently, for projects requiring RDRC review, the City recommends applicants to hold a pre-application meeting with neighbors or notify them by mail. This step would be maintained as a part of the proposed neighborhood notification process. However, a meeting would be required, and notification cannot happen only by mail.

The pre-application meeting would only be required for projects that must go through the neighborhood notification process, i.e., meet the thresholds. For projects below these thresholds, a pre-application meeting will not be required.

Prior to the pre-application meeting, applicants will be required to send mailed notifications to all property owners residing within a 300 feet radius of the subject property. These notifications will need to include details about the proposed project and extend invitations to attend the pre-application meeting for further information.

During this meeting, applicants will be expected to provide attendees with project details, offer opportunities for input, address concerns, and potentially incorporate suggestions into design revisions before formally submitting the application to the City.

This is a critical step in the process because it provides neighbors with the opportunity to provide input into the design before a formal application is submitted. The applicant is more likely to make changes to their design at this preliminary stage.

8.a
October 23, 2023 Packet Pg. 201
• Step 2: Application Submittal
As part of the formal planning application, the applicant will be obligated to include a copy of the neighborhood notice, meeting minutes, and sign-in sheet(s) from the pre-application meeting. Furthermore, the applicant will be required to outline any concerns that were raised during the pre-application meeting and explain how these concerns will be addressed, or if not, provide reasons for not addressing them. • Step 3: Neighborhood Notification and Public Comment Period After the applicant submits a formal planning application, the City will mail a notice of application to property owners within 300 feet of the site. This notice will include contact information of the assigned City planner and the project applicant. If a neighbor has a concern, they will be able to contact the City planner or the applicant within 14 calendar days from the notice of application is received. Additionally, the applicant will be required to post a yard sign on the project site when the notice of application is mailed. The sign will be required to remain posted until the project is approved. • Step 4: Project Approval
After the 14 calendar days end, project applicant will need to provide comments received to the assigned City planner. If no comments are received, the project will be deemed approved. Applicants will then be able to apply for building permit(s).

If comments are received, the assigned City planner will review the comments to determine if the project meets the objective design standards and if any changes can legally be required in order to meet the standards. Once the applicant makes changes, as needed, the project will be deemed approved, and the applicant will be able to apply for building permit(s). Following Planning approval, City staff will update the project webpage to signify project approval.

Please refer to Attachment 6 summarizing the new neighborhood notification process.

How will the community be informed about the new compliance review procedures? The proposed compliance review process would be a significant change for applicants and the San Carlos community. If the proposed compliance review process is approved, staff will prepare a “Neighborhood Notification Information Packet” which outlines the review thresholds, steps, and applicant requirements. This packet is referenced as part of proposed zoning amendments to Chapter 18.29 - Design Review and Objective Design Standards Compliance Review of the San Carlos Municipal Code. (Attachment 1)
Staff would conduct extensive education and outreach initiatives to share more information about the new process. This can include:
• Information posted on the City’s website.

8.a
October 23, 2023 Packet Pg. 202
• Information in City newsletters, such as the City Council newsletter, the Good Living Newsletter, and the ACC newsletter.
• A letter mailed to all property owners.
• Information at the Farmers’ Market booth.
• Social media outreach.
• List of frequently asked questions (FAQs) posted on the City’s website. • Other outreach efforts.

Evaluation
If the new compliance review process is adopted, City staff will return to the City Council in six months and again at one year after the adoption date to provide the City Council with an evaluation of the process and any recommended changes. These revisions could involve clarifying specific code sections, adding definitions, or introducing criteria to facilitate the interpretation and implementation of the review processes.

Proposed New Section 18.23.310 Standards of Specific Uses (Urban Infill Units) The proposed new Section 18.23.310 incorporates permanent standards for urban infill units (SB9 Units). Currently, the City has an Urgency Ordinance in effect with objective standards for urban infill units, which expires in December 2023.

On June 7, 2023, the PTC3 held a Study Session on urban infill units (SB-9 Units). The PTC recommends the following changes to the Urgency Ordinance text.

Topic 1: Urban Infill Unit Size
• PTC Recommendation: No specific floor area limit on urban infill units; instead, the units be allowed up to the maximum allowable floor area (MFA), which applies only in RS-6 Zoning Districts.

The Commission discussed creating a limit for the RS-3 Zoning District; however, these are larger lots and have a stricter lot coverage limit than lots in the RS-6 Zoning District.

The lot coverage maximum for RS-3 lots is 35% (unless located within the Hillside Overlay District which has a lot coverage of 25%). The lot coverage maximum for RS-6 lots is 50%.

The stricter limits in the RS-3 Zoning District will help to regulate unit size. • The proposed Ordinance allows urban infill units to utilize maximum floor area in the RS6 Zoning Districts, and no floor area limit for RS-3 Zoning Districts.

Topic 2: Basements
3 The staff report, meeting video, and meeting minutes for the June 7, 2023 PTC Commission can be found here: https://cityofsancarlos.primegov.com/Portal/Meeting?meetingTemplateId=13209

8.a
October 23, 2023 Packet Pg. 203
• PTC Recommendation: Remove the prohibition on basements for urban infill units. • The proposed Ordinance removes the prohibition on basements.

Topic 3: Unit Type
• PTC Recommendation: Continue to allow a maximum of two units on each subdivided parcel that utilizes SB-9 provisions; however, allow any configuration of those types of units. This would result in one of the following outcomes:
• A primary dwelling unit and an urban infill unit.
• Two urban infill units.
• A primary dwelling unit and an ADU.
• A primary dwelling unit and a JADU.
• The proposed Ordinance allows maximum two units in any of the above configurations on each subdivided lot.

Public Notice and Public Comment
This City Council meeting was noticed per state law on October 13, 2023, published in the San Mateo Daily Journal on October 12, 2023, and advertised through various mediums (social media, website, and email lists).

Staff has received several public comments on topics related to this item including:
• The discontinuation of the Residential Design Review Committee, • Overall house sizes in San Carlos, and
• The recommendation to introduce daylight plane standards – City staff does not recommend including daylight plane standards; additional information provided below.

All comments received, as of October 18, 2023, are included in Attachment 4.

Background on Daylight Plane Standards
In 20174, a comprehensive analysis of house sizes was undertaken in San Carlos, and at that time, the City Council considered daylight plane standards. During that process, the Council chose not to adopt daylight plane standards to control building massing and design articulation.

The rationale behind this decision stemmed from concerns that daylight planes impose a rigid framework that confines building designs, potentially yielding standard "wedding cake" building configurations. The adoption of daylight plane standards curtails architectural flexibility and imposes predetermined forms on massing.

Furthermore, in response to public comments received for the objective design standards project in 2023, staff conducted research on peer cities that mandate daylight plane regulations. 4 More information on the 2017 house size study can be found using this link: San Carlos 2017 House Size Study, CA (cityofsancarlos.org)

8.a
October 23, 2023 Packet Pg. 204
Interestingly, most cities do not impose a second-story setback requirement, in contrast to San Carlos, where the second story is required to have a 9'-0" setback. This, in effect, achieves a similar outcome to what a daylight plane standard would achieve.

Although daylight plane standards establish a basic zone for sunlight penetration to the ground, the quality and timing of sunlight are significantly influenced by various factors such as lot orientation, landscaping, and neighboring structures. It is important to note that daylight planes lack universality, as these standards cannot universally address all contexts. Furthermore, relying solely on minimum side yard requirements does not necessarily guarantee a satisfactory level of sunlight exposure for adjacent properties at the ground level. Consequently, staff holds the opinion that incorporating a daylight plane standard would not necessarily result in aesthetically pleasing designs. Due to this, staff recommends that the Council does not adopt a daylight plane standard to regulate height, massing, light, and privacy.

ENVIRONMENTAL DETERMINATION:

The zoning amendments proposed in the draft Ordinance are within the scope of activities identified in the San Carlos 2030 General Plan Program Environmental Impact Report (EIR) and 2023 Housing Element Environmental Impact Report; therefore, no additional environmental review is required pursuant to Public Resources Code Section 21166 and California Environmental Quality Act (CEQA) Guidelines Section 15060(c)(2) “Preliminary Review” and Section 15061(b)(3) “Common Sense Exemption.” In addition, Government Code Sections 65852.21(j) and 66411.7(n) conclude that an Ordinance adopted to implement Senate Bill 9 (SB9) is not a project under CEQA.

NEXT STEPS:

Should the City Council introduce the Ordinance this evening, the proposed Ordinance would return for formal adoption on November 13, 2023. If adopted, the proposed amendments would become effective 30 days after adoption. At that point, the current SB-9 Urgency Ordinance will become null and void.

ALTERNATIVES:

The alternatives available to the City Council include:

1. Introduce an Ordinance amending San Carlos Municipal Code Title 18 - Zoning: Chapter

18.03 - Rules of Measurement; 18.04 - Residential Districts; 18.12 - Hillside Overlay District; 18.15 - General Site Regulations; 18.20 - Parking and Loading, 18.26 - Planning Authorities; 18.27 - Common Procedures; 18.29 - Design Review; 18.40 - Use Classification; and 18.41 - Terms and Definitions; and adding a new Subsection:

18.23.310 - Urban Infill Units, Under 18.23 - Standards for Specific Uses and Activities; or

2. Do not introduce the proposed Ordinance; or

3. Provide staff with alternative direction.

8.a
October 23, 2023 Packet Pg. 205
Respectfully submitted by:

Al Savay, Community Development Director
Approved for submission by:
_______________________
Jeff Maltbie, City Manager
ATTACHMENT(S):

1. Proposed Ordinance
Exhibit A to Ordinance – Proposed Amendments to Title 18

2. Planning and Transportation Commission Resolution PTC 2023-16

3. Community Outreach Summary and Meeting Minutes

4. Public Comments, as of October 18, 2023

5. Zero Lot Line Analysis

6. Summary of “Neighborhood Notification” Process

7. Public Hearing Notice

8.a
October 23, 2023 Packet Pg. 206
ORDINANCE NO. ____

AN ORDINANCE OF THE CITY OF SAN CARLOS TO CREATE

OBJECTIVE DESIGN STANDARDS FOR SINGLE-FAMILY DEVELOPMENT BY AMENDING SAN CARLOS MUNICIPAL CODE TITLE 18 – ZONING: CHAPTER 18.03 - RULES OF MEASUREMENT; 18.04 - RESIDENTIAL DISTRICTS; 18.12 - HILLSIDE OVERLAY DISTRICT;

18.15 - GENERAL SITE REGULATIONS; 18.20 - PARKING AND LOADING;

18.26 - PLANNING AUTHORITIES; 18.27 - COMMON PROCEDURES; 18.29 - DESIGN REVIEW; 18.40 - USE CLASSIFICATION; AND 18.41 - TERMS AND DEFINITIONS; AND ADDING A NEW SUBSECTION 18.23.310 - URBAN INFILL UNITS, UNDER 18.23 - STANDARDS FOR SPECIFIC USES AND ACTIVITIES.

SECTION 1: The City Council of the City of San Carlos does hereby find and declares as follows:

WHEREAS, recent changes to state law (Government Code Section 65589.5, SB 35, SB 330, SB 9) require that cities adopt and ministerially act on residential development applications based on whether the project complies with objective design standards; and WHEREAS, on January 23, 2023, the City adopted the focused General Plan Housing Element identifying policies and actions to accommodate additional residential units and to eliminate impediments to the creation of more housing; and WHEREAS, the City currently relies on a combination of objective and subjective design standards, implemented through a design review process with staff, the Residential Design Review Committee (RDRC) and Planning and Transportation Commission (PTC) and sometimes City Council to regulate the design of applicable housing projects; and WHEREAS, there is an immediate need for the City to update its standards for all residential projects to ensure orderly, streamlined development in an effort to be in compliance with the state law and help meet the Regional Housing Needs Allocation (RHNA) of at least 2,735 new housing units; and
WHEREAS, on May 4, 2022, the City conducted a community workshop to introduce the project and identify neighborhood elements that are integral to the character of San Carlos and where walkability, safety, diversity in design, availability of open and green spaces were discussed; and
WHEREAS, on June 6, 2022, the PTC and RDRC conducted a joint study session to receive an update on the progress on the standards and SB 9 permanent ordinance, provide input on the emerging standards for single-family developments, received public comments, and identified and provided direction on the overarching elements that are most valued by the community through the objective design standards project; and WHEREAS, on Monday November 28, 2022, the City Council approved the extension of the SB 9 Urgency Ordinance for a period of one year to December 2023 to adopt the Permanent SB 9 Ordinance with the citywide objective design standards as this approach would result in one

8.a
October 23, 2023 Packet Pg. 207
set of objective design standards for all residential development, which includes single-family, SB 9, accessory dwelling units (ADUs), and duplex and townhouse development types; and WHEREAS, on January 31, 2023, a citywide online survey was published and advertised through the City’s website, e-notify, social media and citywide postcards to encourage public participation, comments, and input on various design aspects pertaining to single-family objective design standards, over 420 responses were received; and WHEREAS, on March 20, 2023 and May 3, 2023, the PTC conducted study sessions to discuss preliminary draft standards and specifically studied the articulation, massing, setback and step back requirements, received updates on the progress made to the draft recommendation, received public comments and provided direction on developing the final single-family objective design standards; and
WHEREAS, on June 7, 2023, the PTC conducted a study session specifically focused to discuss regulations to be incorporated within the permanent SB-9 Units (Urban Infill Units) Ordinance pertaining to their maximum permitted size, applicable objective design standards to Urban Infill Units, received public comments and provided direction to staff to integrate the new Urban Infill Units chapter within the municipal code in conjunction with the objective design standards project, thus recommending to replace the Urgency Ordinance, and WHEREAS, throughout the process, staff conducted meetings and outreach with subject matter experts through two stakeholder meetings and two roundtable meetings with peerarchitects and received valuable feedback on the preliminary recommendations; and WHEREAS, prior to the community workshops, survey, study sessions and public hearings, City of San Carlos staff conducted robust community outreach to encourage maximum participation. This included social media posts on San Carlos’ Facebook, Nextdoor, Instagram, and Twitter accounts. Announcements about the project and workshops were made at public meetings of the City Council, PTC, and RDRC. In addition, the public participation opportunities were promoted through the City of San Carlos Spotlight Newsletter, citywide postcards, Good Living Newsletter, and San Carlos’ e-notify (email) communication; and WHEREAS, pursuant to Government Code Section 65853 and 65850 and San Carlos Municipal Code Chapter 18.136, when a change in the Zoning Ordinance (Title 18 of the San Carlos Municipal Code) is found necessary, the PTC shall hold a public hearing to consider such change and render its decision to the City Council; and WHEREAS, pursuant to San Carlos Municipal Code Chapter 18.136.030 and California Government Code Section 65090 and 650901 a public hearing notice was published on June 5, 2023, for the Draft Zoning Ordinance and the San Carlos Municipal Code Draft Amendments in the newspaper, distributed to interested agencies, added to the City’s website and announced through e-notify, citywide postcard, and other social media platforms; and WHEREAS, the PTC conducted a public hearing on amendments to the San Carlos Municipal Code to hear and consider all comments of all persons interested in or concerned with a proposed amendments of Title 18 of the City of San Carlos Municipal Code on June 19, 2023 in consideration of a recommendation to the City Council regarding adoption of an Ordinance; and

8.a
October 23, 2023 Packet Pg. 208
WHEREAS, the proposed amendments would help to ensure orderly, streamlined residential single-family development while being compliant with the state law; and WHEREAS, the City Council has received a recommendation from the PTC as a result of a Public Hearing held at the PTC Meeting June 19, 2023 and has considered the recommendation of the PTC for regulations in the San Carlos Municipal Code including PTC findings for amendments to the Title 18 and the reasons for the recommendations, the relationship of the proposed ordinance or amendments to the Zoning Ordinance (Title 18), and 2030 General Plan and 2023 Housing Element; and
WHEREAS, the City Council finds that the desired outcome of the Ordinance update is to ensure orderly and streamlined residential single-family development while being compliant with the state law; and
WHEREAS, the City Council finds the Ordinance update process evaluated current issues and successes with the existing ordinance and explored options for changes based on evidence and best practices in other communities and industry experts; and WHEREAS, the City Council finds that the preferred options were identified with the goals to increase clarity, efficiency in review procedures, and effectiveness of Ordinance implementation, and adopts the following amendments to the San Carlos Municipal Code Title

18. SECTION 2: Findings. The City Council makes the following findings:

A. The proposed ordinance amendments are consistent with the General Plan.

The recently updated 2023-2031 Housing Element includes the following goal:
• Goal HOU-4 which states: “Remove or mitigate governmental constraints inhibiting the provision of adequate, affordable housing throughout San Carlos.” Basis for Finding: The proposed amendments include revisions to the design review chapter to help enhance the efficiency of the review procedures for single-family development. These changes aim to streamline the project review process, ultimately facilitating the faster generation of housing. As such, adoption of the proposed Ordinance amendments will facilitate an efficient project application process and high-quality residential development in San Carlos and comply with State objectives and law.

B. The ordinance amendment is consistent with the purpose of the Zoning title to promote the growth of the City in an orderly manner and to promote and protect the public health, safety, peace, comfort and general welfare.

The recently updated 2023-2031 Housing Element includes the following action:

8.a
October 23, 2023 Packet Pg. 209
• Action HOU 4.4 outlines action to prepare Objective Design Standards for residential developments by reviewing the Zoning Ordinance and crafting revisions that support objective design standards consistent with the Housing Accountability Act.

Basis for Finding: The proposed Ordinance amendments proposes to objectively regulate, as required by State Law, building materials, massing, articulation, landscaping, and parking design consistent with the General Plan policies identified below.

The 2030 General Plan Land Use Element also includes:
• Goal LU-8, “Ensure excellence in all development design.” The policies identified to achieve this goal that are consistent with the single-family objective design standards project includes:
o LU-8.1 “Require all development to feature high quality design that enhances the visual character of San Carlos”,
o LU-8.2 “Ensure that new development is sensitive to the character of adjacent structures and the immediate neighborhood”;
o LU-8.5 “Optimize architectural quality by encouraging the use of quality materials, particularly as accents and authentic detailing, such as balconies and window trims”;
o LU-8.7 “Require new residential development to provide outdoor areas and landscaping or native vegetation, or tree canopy to enhance the surroundings”; o LU-8.10 “On all sides of buildings, require the incorporation of quality architectural design elements for all building façades and stepping back upper floors in order to reduce bulk and mass and to break up monotonous wall lines”; o LU-8.12 “Require residential building entrances to be related to the street”; o LU-8.13 “Require parking areas associated with development to be located and designed to minimize visual impact to the greatest extent feasible. This may include locating parking behind buildings street frontage, below grade, or screening through the use of natural landscaping”;
o LU-8.19 “Residential structures shall be designed to be compatible with existing structures in the vicinity, avoid obstructing views from adjacent structures or views of community importance, avoid interference with the right or ability to use solar energy and be consistent with the community design principles”.

Basis of Finding: The proposed amendments address the neighborhood character through objectively regulating the architectural design elements and Hillside Overlay requirements while being consistent with the General Plan goals and policies.

The General Plan 2030 Land Use Element includes the following goal:
• Goal LU-9 stating, “Protect and enhance all residential neighborhoods”, and Goal LU-10, stating, “Minimize the impacts of development in hillside areas”.

Basis of Finding: The proposed zoning amendments address the neighborhood character through objectively regulating the architectural design elements and Hillside Overlay requirements while being consistent with the General Plan goals and policies.

8.a
October 23, 2023 Packet Pg. 210
NOW, THEREFORE BE IT RESOLVED by the City Council of the City of San Carlos as follows:

SECTION 3: Replacement of Code. The City Council hereby approves the Municipal Code Ordinance Title 18 amendment attached as Exhibit A to amend San Carlos Municipal Code Section 18.03 (Rules of Measurement), 18.04 (Residential Districts), 18.12 (Hillside Overlay District), 18.15 (General Site Regulations), 18.20 (Parking and Loading), 18.26 (Planning Authorities), 18.27 (Common Procedures), 18.29 (Design Review), 18.40 (Use Classification), and 18.41 (Terms and Definitions) and adding a new subsection 18.23.310 (Urban Infill Units) under 18.23 (Standards for Specific Uses and Activities) for the creation of single-family objective design standards. This Ordinance in part replaces the terms of Urgency Ordinance #1595, which shall become null and void as of the effective date of this Ordinance.

SECTION 4: Pending Applications. As to planning applications for new homes and residential additions, which have been submitted and deemed complete, processing, or under review before the Ordinance goes into effect, such applications, may continue, and shall not be subject to the regulations and requirements listed in Exhibit A. Notwithstanding the above, a planning applicant may resubmit using the new regulations once they become effective.

SECTION 5: California Environmental Quality Act Determination. The City Council hereby finds that this Ordinance is not subject to the provisions of the California Environmental Quality Act (“CEQA”). The proposed amendments to the San Carlos Municipal Code as mentioned above are within the scope of the activities and impacts identified in San Carlos 2030 General Plan Program Environmental Impact Report (EIR) and no new environmental effects have been found and no new mitigation is necessary. Therefore, no additional environmental review is required pursuant to Public Resources Code Section 21166 and California Environmental Quality Act (CEQA) Guidelines Section 15060(c)(2) Preliminary Review and Section 15061(b)(3) “common sense exemption”. In addition, Government Code Section 65852.21(j) and 66411.7(n) concludes that an Ordinance adopted to implement Senate Bill 9 is not a project under CEQA.

SECTION 6: Severability. If any section, subsection, sentence, clause, phrase, or portion of this Ordinance is for any reason held to be invalid or unconstitutional by the decision of any court of competent jurisdiction, such decision shall not affect the validity of the remaining portions of this Ordinance. The City Council of the City of San Carlos hereby declares that it would have adopted this Ordinance and such section, subsection, clause, phrase, or portion may be declared invalid or unconstitutional.

SECTION 7: Publication and Effective Date. This Ordinance shall be published and posted according to law and shall take effect and be in force from and after 30 days after its passage and adoption.
* * * *
I, City Clerk Crystal Mui, hereby certify that the foregoing Ordinance was introduced on the 23rd day of October, 2023 and passed and adopted as an Ordinance of the City Council of the City of San Carlos at a regular meeting thereof held on the ____ day of ____, 2023 by the following vote:

8.a
October 23, 2023 Packet Pg. 211
AYES, COUNCILMEMBERS: ____________________________________________________ NOES, COUNCILMEMBERS: ___________________________________________________ ABSENT, COUNCILMEMBERS: _________________________________________________ ________________________________
CITY CLERK of the City of San Carlos
APPROVED:
____________________________
MAYOR of the City of San Carlos
Exhibit A: Proposed Amendments to Title 18

8.a
October 23, 2023 Packet Pg. 212
 


  
 



!" #$% &'#(% )%*+",!( *+#"%-+. %/-$01/$-!2$$-$%/ -%/!#3!2.!#*30 +"!,-$,$" *# 4% )% %$%/ 5!#6!-$"70#+2+,!6$* 8+% 9:;8/ 0" $<,0-, =,+#.=!#*1- #% )%*$ "#$%2!--(!#(", 2+>2 ? !#+#1;
@ABBCDEFGHDFIFJKLMBKNLBKNOJOF@PQPRSOTKUV
@CNPCDTFJQANSWSICTPFLKPXCIOKDJ@ABBCDEFGHDFIFJKLMBKNLBKNOJ U YZ[\]^_`abcdefbgc`hbibjklmaghneonjpkqbh`abdedrbhgaaqbnpqkibgc`hbibjk[ s YZ[\t^_bcnubjkngavnckhnwkcl
fgxnjpbyncknjpubcnpjckgjughucdz{bwknrb|guunjp
dz{bwknrbubcnpjckgjughucedhu`}abybc|
kd~jqdibcgjugibjunjpkqb`cbkgzab[
 YZ[Y€^naacnub‚rbhagovnckhnwkl
maghneonjpkqbƒ„gk`hga
kgkb†hb‡`nhbibjk|
ibgc`hnjpqbnpqk|gjuud~jqnaaegwnjpegˆgubckb}
zgwx[
‰ YZ[YŠ^‹bjbhga
nkb_bp`agkndjcl
Œaad~njp}dhwqbckdzbwadcbhkdkqbcnub~gaxzo
gibjunjpkqb}dhwq}hd{bwkndjgaad~gjwb
unibjcndj[
 YZ[€\^Žghxnjpgjudgunjpl fduneonjpuhnrb~go}ghxnjphb‡`nhbibjk~qbj }hd}dcnjpgdjbwghpghgpb[
‘ YZ[€’^ŽagjjnjpŒ`kqdhnknbcl
khnxnjphdabcgjuhbc}djcnznanknbcdekqb_bcnubjknga
vbcnpj_brnb~mdiinkkbb^_v_ml[
“ YZ[€”^mdiidjŽhdwbu`hbclŒibjunjphdabcgjuhbc}djcnznanknbc[ V YZ[€•^vbcnpj_brnb~l _bidrnjp_v_mhbrnb~hb‡`nhbibjk|njkhdu`wnjp gjb~jbnpqzdhqddu„dknenwgkndj}hdwbcc[
– YZ[t\^—cbmagccnenwgkndjl fduneonjp`cbwagccnenwgkndjcedhcnjpabeginao ubrbad}ibjk|guunjp—hzgj˜jenaa—jnkc`cbko}b[
U™ YZ[tY^šbhicgjuvbenjnkndjcl Œuunjpjb~ubenjnkndjcc`wqgcad~bhckdho~gaa| jgk`hgackgkb|bkw[
UU ›œžœŸ ¡¢£¤YZ[€][]Y\^
kgjughucde

}bwnenw—cbcl
˜jkhdu`wnjpgjb~cbwkndjubunwgkbukd—hzgj˜jenaa
—jnkc^
¥•`jnkcl[
9 8.a
October 23, 2023 Packet Pg. 213





!

"#$%

&
'()$*+%+$(%

,+$(%

-
%#+(./+%(,%

0 %#+(.+.

1 %#+(.)$2+/(//

3 45+(+(.*.%)$

45+(+(.6$$

7 45+(+(.6$$+$

45+(+(.)$,$*.

45+(+(.)$8$(.

&
45+(+(.%9,:%;</%=

%#+(.%+.(%

-
%#+(.:+(.)$)(/%,+(.

0 %#+(./%+(,)(,

0 %#+(.+.

>?@A BC
DEB
FG
DH
DI
?EB
FG
DI
DI

IJC

AFG

AKA BCG
L
M
N
I
O
IGDCAGPDC
BGQFJFAG
II
DI
R

L
I
CB
BCG
C
FSAM
JTU
IC

LMAK
LAVA

C

LU
IGWF

LAKA ACGC

L
C
II
DI
RAW
CDAMF
LAR

IG
CI
RRGC

LXUBF

ICN
 R
OG

I
Y

F??Z
CRBCR

L
I
CBFU
IPDC
BGQFJF

IF
N

L
IL
FF
N
D

ICFJF !
IBCMFJFU
I
AMF
IG
CKA
C
DCAG
L
BCM[

U
C
IO
IGDC
BG
FJFAG\

D
IMB
FG
D
L
IMB
FG
D

MAWK
C
IA
L
LC
K
I
C
C
DI
]
L]NAS?
^'

0 _`^'a^4^'b^'b
c?@A BC
DEB
FG
DH
DI

F
RGd

?eF

N

IADCAGIAD
L
RC

CK
C
M
N
ILC

AGCACF

F
 U
C
IK

G

A
R

LC
K
ILC

F

F
NI
IC

f

8.a
October 23, 2023 Packet Pg. 214
 


 


 


 


 






!"#$%#$&$'()!*+, (-

.
/

01 .
2 234.-045 1043-
678 9  


 
 






:


;
  
 






 <
 8


 = >?>@ABA
C

8 
DE
 F

= D

 G 
 


  

 
 
H
>9
 II  



;8
 J

 
;

 
  

69
 



 

;

 
H
E 8

 K

E 
 



  


!"#$%#$&$'/)L*+1 3 ,
.
.

(/(- , .3
-(-34M
N

8.a
October 23, 2023 Packet Pg. 215
 


 












8.a
October 23, 2023 Packet Pg. 216





!"#

$
%&!#'!()"%#

*
+(",%#%&&#-&)#).#

/01.)+&#)'%#%&&#!(,%('!()"%#-&)#).#

2 +(",%#%&&#-3&)#).#

4 !(,%('!()"%#-3&)#).#

5 #)&%)(&+(",%6#

5 !(7#%&&#

5$"8%"!##%&&#

5*,((9("#!0&)+)#)"%#%&&#

!"#

:;
<=<>?<



@;?
A
BCA
?
B?

DEF?
?GH<?
HB
A
;B
;;B?B?
@;IJK
A@@?
?
A
BC
L;M
?;

A
E
NEO

>?BAP>BCL;HB?HB
A
<

<B@
?B;AQCC
LE
IEO

>?;B;
BCB
AA
L

@
QAGC
<R
B
ABC?B


S

L
?>>?
B?

R<BMCQ;
>??
>
A
L;
R
B
AB<<?
<?B
;<;J
BC;B?B?


@;
B
A;B?B
Q;?;<?
T
<?
<

AE
UEF?
GA

@
?<>MCB
A
RV<>MCCB
A>

H
>;B
<B?W
B
A<>MC
B@J@BC
H;BQCC

?GIJ?
A

B
AQCC
R<CR

>??
>
A
L?
A
BCAGC
<R
E
DAA

BC<>?<



@B;?
A
BCA
?Q;;@
CC
QR<CR
X
?BCFCB
CB

=B

@
Y
LCVZBRCJH[A>\B?H]Y
LCVZBRCJH^A>\B?]Y_>C<CVZBRCJH`aVbcA>\B?H]Y_>C<CVZBRCJH daVaeA>\B?H]B
A_>C<CVZBRCJHfaV`ccA>\B?E]
OEgV[
LCVZBRCJE:;
A
?


AA@
??
A
BCA


><
;?h[i>

<?
B?E
UGC
<R
UQCC
LJ<
RBJ
C>AAB;A

LCV>
;
>

LB
AB

?JAQCC
L>

H


A


LCV>

<>?
>B

X
G?
R
I
A

^ajabEb`B
A^^d``EfhY>?MB

=CC>

]iHA><CS
H
B
A
RBCCC

>MAG


EEk
BAA




LCV>
;
R
H;
A
?<?
GA
@
?>


>;B

RBCCB
A
CB?L@BRCJ;CAB?H<B?WB
A??B

@BC
HB
A
RR>
JLB?A

;BRBJMB<<?
<?B
B


LCV@BRCJ?
A
BC
L;M
?;

AE
ZEgV^
LCVZBRCJE:;
A
?


AA@
??
A
BCA


><

Sh^i>

<?
B?E
UGC
<R
UQCC
LJ<
RBJ
C>AAB;A

LCV>
;
>

LHB

?JAQCC
L>

H


A


LCV>

<>?
>B

X
G?
R
I
A

^ajabEb`B
A^^d``EfhY>?MB

=CC>

]iHA><CS
H

Q
;
R
HB
A
RBCCC

>MAG


E
RBCCC


LCV>
AGC
<R
HA><CS
H
Q
;
R
HB
A
B

?JAQCC
L>

E:;
A
?BC

BCC
Q
@
?>


>;B

RBCCB
ACB?L@BRCJ;CAB?H<B?WB
A
??B

@BC
HB
AGB
A

>

BC>


>;B

;

C
B
A<CB
@
?
RR>
JB

RMCJ;B
RBJMB<<?
<?B
B

LCV@BRCJ?
A
BC
L;M
?;

AE
a

8.a
October 23, 2023 Packet Pg. 217














































!
"
#

$











 




%!  

 
%



%


 

!


 %


 














  



 

%
&



%





 


 

!























'()























*



()







 




 

!


 
















!
"
#









+




 

!  

 












"









, 

!




 






-



 












.






%












 !
!



!

  
%
!




%





























/0(1230
4"-
%05/0(11
4"6



%7/0(89
4"6



%027/0:2

4"6



%0(7/0:823:
4"-



%00

.0
























 
0







 




 

!


 






"

*
, 




-


 













.






%












 !
!




!

  
%
!




%




























;<=>?=>@>ABCDEFGHGIEJBKLMCF=NOPQROSTTUVWNOPQROSXUVT
!
02:

!

 



















!

!








7
YZ[




 
Y[

 

*













 


!

\
 -




Y][

 

*


















!

Z

 ]


Y
^
[ !





*












!

Y[

 






_

*

*
]

02:%_]

*

.


*
 




*%
$






 




*




 !










_

*

 !

*







!

 
!
 !









 !



!


!















  +

 !













1 8.a
October 23, 2023 Packet Pg. 218






!"#"$%"

%"&'%"

((

!)*
!
+,-./,01.234-,-
+,-./,01.23567-.089:;,-<,,-7=>32--.?>21.60-=,36@ <.083,A40.1B@,33.08CCAAA <,,<,>1.60DEFGHFGIJK<L233361
<7=/.M.-.60-120/2N/-
O
<,,<,>1.60DEFGHFGIGK+,-./,01.23
/,M,36;L,011:;,-F
<,,<,>1.60DEFGHFGIDKB7;3,P
-120/2N/-
<,,<,>1.60DEFGHFGIQK96@0R67-,
-120/2N/-
ST6N16@0R67-,/,M,36;L,01.0+U /.-1N.>1-KB,M,36;L,01<120/2N/-6V +UB.-1N.>1-R2332;;3:
<L233W61<.083,A40.1
<7=/.M.-.60B,M,36;L,01

AXYDZ XYDZCXYQZXYQZ
[708236@X67N1AXYDZCXYQZXYQZ
\>>,--6N:B@,33.0840.1CCCCC
]70.6N\>>,--6N:B@,33.08

40.1 CCAAA
B7;3,P CA CXCAA
4N=20^0?3340.1-CCAAA
96@0R67-,B,M,36;L,01AXCS CS CS
U731.A40.1+,-./,01.23AACCC
_3/,N3:20/W608A9,NLX2N,AAAXX
T2L.3:B2:X2N,<,,-7=>32--.?>21.60-=,36@ <L233 CCCCC
W2N8, CCCCC
`N67;+,-./,01.23AAACC
+,-./,01.23X2N,T2>.3.1.,-<,,<7=>32--.?>21.60=,36@ I

8.a
October 23, 2023 Packet Pg. 219




 








!"##$ $ $ %

%
&'()*+,-.,-//01
2(3
'(!"
&!
4!&("('(
2 5(6('
377777
%
() ##$ $ $ %

%
&'()*+,-.,-//01
2(3
'(!"
&!
4!&("('(
2 %(8"
1))69&&:;!&<##===%

%
&'()*+,-.,--/0%(8"
))6 )&&:;!&<>)'
"2
? !2('()!"@):2(877777%

%
&'()*+,-.,-A/0? !2('()!"
!32:;;) '(B
>):2(8
%:;;) '(B
@):2(877777%

%
&'()*+,-.,-A/0? !2('()!"
!32:;;) '(B
>):2(8
7:C"(&!3%
6(#7:C"(&D2
2 =)66:('<E22
6C"<#=#==%

%
&'()*+,-.,/+/0=)66:('<
!22
6C"<4!&("('(
2 =)66:('<
! 3
77777
=:"': !"F2'(':'()#=#==
G!<=!
=
'
2###7 7 %

%
&'()*+,-.,/H/0G!<&!

7! I!31
&
!'()
J!&("('(
207:C"(&
77777
7:C"(&%!4
'<J!&("('(
2#====
%&>))"207:C"(&) 7 (B!'
#====
%)&(!"%
B(&
J!&("('(
2###$ $ +

8.a
October 23, 2023 Packet Pg. 220




 








!"#$%&' '
($)#*+$*,-!#*.#*+
(')$/%#'0 *)'1

*2 *# *"
3 45633 3 7 7 ")#
*89:;5:8<=1>?),

!
,#*#*+
@ )$#%7$% '1

*2 *# *"
A$!. )'
3 45633 3
B!$*'C
!)$)#
*1

?*#"$)#
*1$*,&)#%#)# '&' '

?*#"$)#
*D$"#%#)# '7
0$C) !89:;<1E#! % ''B % "
?*#"$)#
*'D$"#%#)# '
&)#%#)# '1A#*
!FFFFF
>)0 !GCC%#"$/% BHC '
G"" ''
!H&' '$*,
7)!?")?! '
7 7 ")#
*'89:8I:=;=1G"" ''
!H/?#%,#*+'$*,')!?")?! '1$*,89:;5:=5=1
G"" ''
!H?' '
J
>""?C$)#
*'FFFFF7 7 ")#
*89:;5:8;=1J

""?C$)#
*'
K
*"
*L
!#*+&'
0$C) !89:8M1K
*"
*L
!#*+&' '17)!?")?! '1$*,N
)'
B C
!$!H&' 7 7 ")#
*89:;5:;<=1B C
!$!H?' '
7C "#O"N##)$)#
*'P
8:Q*$,,#)#
*)
')$*,$!,?' C !#)O*,#*+'1)0 F%$**#*+

#''#
*?')O*,)0$))0 , 2 %
C *)#', '#+* ,
R#)0$''#*+$*,0 #+0))0$)#'' *'#)#2 )
)0 /?#%,#*+C$)) !*
L)0 $! $$*,$,S$" *)C!
C !)# ':
;:Q*$,,#)#
*)
')$*,$!,?' C !#)O*,#*+'1)0 F%$**#*+

#''#
*?')O*,)0$)'C "#O"'#) "
*,#)#
*' T#')
'?"0)0$))0 C!
C
' ,, 2 %
C *))HC #' U?$%)

!/ )) !)0$*?%)#3?*#)! '#, *)#$%
!)
R*0
?' , 2 %
C *)
)HC 'R#)0! +$!,)
, '#+*$*,$"0# 2$/% , *'#)H$*,)0 C!
S ")#', '#+* ,R#)0$''#*+$*,0 #+0))0$)#'' *'#)#2
)
)0 /?#%,#*+C$)) !*
L)0 $! $$*,$,S$" *)C!
C !)# ':
5:7?/S "))
)0 L
%%
R#*+%##)$)#
*'P
$:N##) ,)
"$L '1"
LL '0
C'1, %#'1$*,* #+0/
!0

,$!. )':D?%%' !2#" ! ')$?!$*)'$! *
)$%%
R ,:
/:N##) ,)

* )0
?'$*,O2 0?*,! ,'U?$! L )
L'$% '$! $:
":J
?!'
L
C !$)#
*$! %##) ,)
/ )R *' 2 *$::$*,*#* C::
,:A?')/ %
"$) ,R#)0#*$)R
3')
!H/?#%,#*+:

M

8.a
October 23, 2023 Packet Pg. 221
















 















 
 



!
"


#
$


!

#
#


#



%










&





'

# 












'

 


 %#



(

#
#
)*
+,-.)/
01


'*
+,,)/
2)#
11


'*
+34)/
2)#
11

-5*
6-)/
2
)#
11

+'*
63-.6)/
0)#
11

1
789:;9:<:=>?>@ABC>DEFEGDHGIHFJKLHMFEIMNEFOPQRSTQUVVWXY
Z
 -63#


#




[\

0














\








 
 









 %


 Z

 


 

#



]^_







 




\





Z








## %





#
## 



[\

$
#



##
(



# %


#


(











"
%

##








(

 %
`
 


#


#-
-)`
 


1


-
a)[

*(
\




# 

[1
  

#
!
Z
 -6
b

[

[


c
#
#


#
(








(







## 



(


[#



#-
a


\(

[0%
## 










#

 
(








(

[






#


#-
a5
de 2








dde 2






ddde 2


!



#
#


 


f

!



"




dge 
%








!


ge /%





%




gde h








f
gdde b



#

gddde $



die [







ie j




8.a
October 23, 2023 Packet Pg. 222






!
"##

$%&'()*'&
$%
+
,-./0123045.67./01/814
9/:5;<; 23045.6
=<05.4>03.
/?83@
AB
9505;<;,-.
75C3=4DEF.E@
GHIHHHJ KIHHHJJL3M4<N15O545-0P-.44Q/PPN34<NR3?.
.-7S9ST/NP3GUEGBEHAH
S-8038,-.4GHIHHHJ BIHHHJJL3M4<N15O545-0P-.44Q/PPN34<NR3?. .-7S9ST/NP3GUEGBEHAH
9505;<;,-.

V51.Q=F.E@
UKJ WHJJL3M4<N15O545-0P-.44Q/PPN34<NR3?.
.-7S9ST/NP3GUEGBEHAH
G
S-8038,-.4UKJ BHJJL3M4<N15O545-0P-.44Q/PPN34<NR3?.
.-7S9ST/NP3GUEGBEHAH
X
9/:5;<;YP--8Z83/
9/:5;<; YP--8Z83/
=9YZ@
L-9YZY-8P-.4P344.Q/0-83D</P.-
UIKHH4DEF.E9YZ54.Q3[83/.38
-FGIGHH4DEF.E\AK]-F.Q3P-.
/83/-8KH]-F.Q3P-./83/^F-8
P-.4[83/.38.Q/0UIKHH4DEF.E
9YZ54KH]-F.Q3P-./83/E
733SQ/_.38G`EHAIa<P34-F
93/4<83;30.^733
73?.5-0G`EXAEXGHF-8/??344-86
1M3PP50[<05./01R<05-8/??344-86
1M3PP50[<05.4./01/814
b<5P150[Y-8;/01,-?/.5-0
9/:5;<; c35[Q.=F.E@X`=Z@X`=Z@73373?.5-0G`EGKEHBHIc35[Q./01 Q35[Q.3:?3_.5-04/01733SQ/_.38
G`EGXF-8_38;5445NP3Q35[Q.M5.Q50/
c5PP4513dO38P/6254.85?.

A
GG

8.a
October 23, 2023 Packet Pg. 223






!
"##

$%&'()*'&
$%
+
,-./01234
56708,-./01
9:6:
;<=>
[email protected]:BC@DE
FGH3@ ;IJ:@5@HGKLJ>BME
;345@HGKLJN
566561@0H3J<DJ>DI<IO,GHP61@0H3:
03@HK2G4:
=
Q3@6G0HG5046J:@5@HGKL
JI
;34
5@HGKLJ=

BROSOTE
J:@5@HGKL>BREBME
;345@HGKLNBSEBROSOTE
>
5@G66@5046J:@5@HGKL
JIBTE
;34
5@HGKLJ=

BROSOTE
J:@5@HGKLUD>BTE
;345@HGKLJJD>BROSOTE
V
W62G ;IJ>BFEU
X2G2Y6OCGH7 ZGHZ6G@K/036
;I;I 566561@0H3[D\D4O6
S6@21]64X2G2Y6:234566R]2Z@6G
J<DJ;CHG^0//:046_`6G/2KS0:@G01@
,GH`0:0H3:
<
X2G2Y6OCGH7 ZG072GK
C21246
>BXE>BXEN
?2a07-7bH@
RH`6G2Y6
B,6G163@HC
bH@E
;>03^ _`6G/2K
\>
H-@:046^ _`6G/2K
>I566R]2Z@6GJ<DI\OW-/6:HC
?62:-G6763@
JI
[DM-0/403Y^60Y]@c0@]03@]6FGH3@234W62GF0C@663F66@HC@]6M-0/403YDd]672a07-7]60Y]@c0@]03 @]6CGH3@234G62GeC@663BJ>EC66@HC@]6.-0/403Y:]2//.6762:-G642:034012@6403561@0H3 J<DI\DI>IB?62:-G03Y]60Y]@E3H@6a166403Y@c63@K860Y]@B;<[email protected]/403Y:/H12@6403@]6 ^0//:046_`6G/2KfH303Y40:@G01@OG6C6G@HR]2Z@6GJ<DJ;B^0//:046_`6G/2KS0:@G01@ED J;

8.a
October 23, 2023 Packet Pg. 224






!"# #$%&'()*'#+$!,-.,/0,$10#11$2&-34$567894##$!-:!"$2;$2#<!-!<=<>/,=-"?@,,/1!"# 1#$%&'(12&00%#&<!-!<=<,4$#-6A89+#/'#-$,4$2#0,$:!"$2,/$2/##6B94##$;:2!'2#C#/!1 >/#&$#/
DE2#=++#/1$,/5<&5&0!>-:!$2$2#0,:#/1$,/5&$$2#/#F=!/#"0,:#/1$,/53C#6794##$1#$%&'(4,/ =+$,$2!/$56B89+#/'#-$,4$2#0#->$2,4$2#0,:#/1$,/5E2#<&*!<=<$2!/$56B89+#/'#-$ +/,G#'$!,-12&00%#<#&1=/#"4/,<$2#/#&/:&00,4$2#0,:#/1$,/5H-5:!-",:0,'&$#",-$2# +/,G#'$!->+,/$!,-,4$2#%=!0"!->12&00%##!$2#/&'0#/#1$,/5:!-",:,/12&00%#>0&I#";$!-$#"; #$'2#";4/,1$#";,/$/#&$#"!-&-51!<!0&/<&--#/$2&$0!<!$1C!#:1!-$,&-"4/,<$2#:!-",:


JJKKLMKNJK
AB

8.a
October 23, 2023 Packet Pg. 225




!"#"$!""%$&#"'#()%*+((#&,,"$-./0.$1".,$,"2"%3456""$6#(7$!"8#(8"#$91&%":$!")88"# ,$(#97.9.1&'%;&$!$!"1(;"#,$(#96(#$!""%$&#"1"%'$!(6$!"-)&1*&%' <=(#.'#()%*+((#,"$-./0(6,"2"%3456""$.8#(>"/$&(%(6)8$($;(3?56""$&,.11(;"*(%$!"1(;"# .%*)88"#,$(#9@!".1&'%7"%$(6$!",$(#&",,!.11%($"A/""*$!&#$93BC58"#/"%$(6$!"1"%'$!(6 $!"1(;"#,$(#9@!"7.A&7)7$!&#$93BC58"#/"%$8#(>"/$&(%,!.11-"7".,)#"*6#(7$!"#".#;.11(6 $!"1(;"#,$(#9D%9;&%*(;1(/.$"*(%$!"8#(>"/$&%'8(#$&(%(6$!"-)&1*&%',!.11-""&$!"#. /1"#",$(#9;&%*(;(#,!.11-"'1.E"*:$&%$"*:"$/!"*:6#(,$"*:(#$#".$"*&%.%9,&7&1.#7.%%"#$!.$ 1&7&$,2&";,&%$(.%*6#(7$!";&%*(;
FGH$#""$H&*"H"$-./0,(%I($,;&$!J"2"#,"*=#(%$.'"@!""A$"#&(#,&*","$-./0&%$!"#".# $;"%$9KL2"8"#/"%$(6.#"2"#,"*/(#%"#1($,!.11%($-"1",,$!.%$!"6#(%$9.#*#"M)&#"*(# "A&,$&%':;!&/!"2"#&,1",,:(%$!".*>(&%&%'0"91($
NO

8.a
October 23, 2023 Packet Pg. 226





!"#!$%&'!%()*+!$%"',-./!"0&1/'2
3!)(!$)('451$).$#5'.564)''$4'')14)('7 !"#!$%*)('
/.8!/ /('!%()2(.""7'$1/15')(.$)9'$)0,'!%()4'')*/'.2 5'#.2.:'5)!;."#!2).$;'451/)('"19'2) 6$!2('#%5.#'.))('7 !"#!$%4.;')1)(')1</12)<1!$)14)('5114

=>

8.a
October 23, 2023 Packet Pg. 227




!"#$% $ "&'(&)*+,
-.((&/("&0123(4(+("& 5 ( 6&.(% &7 "&.(7*5()% +,6*+(.*3( )(("854 3(#/8&.)!8%#8"97:&.(58"85!59 !"#; 6 "&7(&)*+,(<!8(5("&7.*%%)(&.(*3(*9( 6 &.(*+&!*%6 "&7(&)*+, 6*%%854 3(#% &7 "7!+.)% +,6*+( 26&(("6((&:/.8+.(3(87%(77

=
>* /? &'8#('(&)*+,
@.(58"85!59 !"#; 78#(7(&)*+,6 % &7/8&.*"*3(*9(/8#&. 6 6 &0123(6((& %(777.*%%)(*58"85!5 6&("4(+("& 6&.(% &/8#&.: &.((6((&:/.8+.(3(879(*&( A
B
'(+ "#'& 0C D(+&8 "
@.(!44(7& 05*0*%89"/8&.&.(% /(7& 0 4 D(+&*5*E85!5 66 ! 6((&8"& &.((<!8(#7(+ "#7& 07(&)*+,6 !4& &.8&04(+("& 6&.(%("9&. 6&.(% /(7& 0

FG

8.a
October 23, 2023 Packet Pg. 228








!"#$%&'(&
%)
*+
,

%
-
&'
".
/*

0 &
%
%

!"#$'
*

"

)
'
123,

4 #
'
&5"

,

%
#&
'

6&
%*"66'&
!
6 %%
*"'
*
5 &'
1"

78 &

0%
'.9)*#*
,

%6
%%9
&'
*
" :&''.$
16&

;<

8.a
October 23, 2023 Packet Pg. 229






     




 
   











   





!

 !


 




   






 

 





 




" 








  

   







#$ 

$ 




 
   
$


 

   

%
 



&

 






 

"'
' '

'


'!




  





 
  
   ()*+,,( !-( ..'/0/01)*+23 ( !-( ..'/0*45)*640( !-( ..'/0*+1)*62476( !8( ..'/0**. 9:;<=;<=<>?@ABCDEAFAGDHIJCKILKMLGNOMJPQQRASAICKRMAHPRKCDOIGTUJ LDGCMDBCG;
8
V

WX  







YZ  [





 





 
  

 %
 



 
 
\Z  




]Z8
 8$8




 



 
 




]]Z









  


 
]]]Z








  



 


 

$

 
 




  

 
'




'

'
*4

8.a
October 23, 2023 Packet Pg. 230








!"#

##$




"
%&$'
'()$')"%*
#
*%')"

%+
',-%)
#
$-'#

"(
$-)"".#

#
)()

'*-,-,
(+)$."*$-$-#

"(
$
$-&$

.!"#

)
#!''
!
#


-.
'-

#

!"#


$')
,
-+'
,+)"
$'/-)""."
,)$#
)0.""
,)$

),

$-$'$)
#-)""

,
'+
')$)+'
1,$

2

%+
',-3
'',%
',
(.
)$

+'
1,$

)
#',)$")$
'$/4!)'
$
)')%*$-)(
(!(#+$-
50$
"$'
)$0#

$-)$,')$)*",
(


$'/)$!'
),

$-$'$%!,-))$'""
'")
#,)+#,
!'$/)'#
$'/%()/.)++'
0#$-'
!
-$-#

'0* +'
,

6

8.a
October 23, 2023 Packet Pg. 231





!"

#$%&'
(

)*
 $+,,$''-

'.,$''/001$.
2#
!$!'
$34

$!1&56766/.8$
9:-;<
=

!>2!
?-
@"

#$%&'-
A"

#$%&..
2,/$'=,4
1,48'?'/001$.$
B
88$!20&82.
2#
!$,,$''82..
2#$!

 $'C,
.2
8'C!.

'.,$'-
AA64
1,48'
$.$
B
88$!.4
'48826/.8$
9;-<D=5
!$%0
!"

#$%&+..
2,/
62'8
4,8
2!E$.

?-
AAA"

#$%&'4.828%$8&=;<?F$$8%
!$
$.$
B
88$!82'$
#$8/$.

B
&4
8-
AGH!$B.

,2I 4
8
2'
$.$
B
88$!%/$20&'
0$J,

 $
'.

2.2'$!
2 $K
'8
-H/$!

#$%&'/001$BK
B4B2F8$=9<?F$$8%
!$!BK
B4B2F
8/

8&J$
/8=L:?F$$8
0$ 8/-
G"

#$%&''$
#
8%22
B2
$4
8''/001$8/$B

B4B%
!8/
$34

$!1&8/$6
8&
M
$$
.$
57765$,8
2'9:-;<-9<<C9;-<D-<N<C!9;-<D-9<<-
GA"

#$%&,,$'',
2'''
!$%0
'
.410
,

/8J2FJ%&'/001$+"+J,2B.0
8-
GAA"

#$%&'1488
'
!$.

2.$
8&0
$'/00
,04!$B

B4B8%2=;?JF228J%
!$
.$
#
24''4
F,$$! $8
$8B$802 8/81488
.

2.$
8&0
$-
GAAA"

#$%&'B4'81$!
'8
4 '/$!%
8/4'$2F!
FF$
$8,202
2 B8$

08/8/$
!O,$8B8$

0
8/$F
28'$81,

$-
AP"

#$%&'2,2
$
028''/001$02,8$!80$'88%$8&=;<?F$$8F
2B8/$.

2.$
8&
0 $'88/$
8$
'$,8
2,2
$
-
;<

8.a
October 23, 2023 Packet Pg. 232







!"#$%
!
&
'(!!

!)*+#,
%!-#$%(!.#$%(
+.#.%(!+#%
$-%(!

!-##.
,!*
*%!!%
$-%(!
+#%/)-%()**)0%12345.!!%#+!**6%(!

!.#$%
!)$,+7-)$ %(!-##/)-%(*(
++$#%!0,!!-

8.%12945:!,!$%#.%(!/)-%(#.%(!.#$%.
,
-!#.%(!;7)+-)$ <"#+#%*/)-!%(
$*)0%12345
.!!%6%(!

!.
=
-!)$,+7-)$ %(!-##*(
++$#%!0,!!-.#%12>45:!,!$%#.%(!.#$%.
,
-!
#.%(!;7)+-)$ <
?@

8.a
October 23, 2023 Packet Pg. 233







!"##$%
&'( )*!$)!!)$*
++*
,!
)'&-+
)'( !+!.!()$&#($'$)'( #%
)+!
$)#(!/01#%
)*!%#++#2'( "!$' (!+!.!()$#()*!%
3 "!4
'
5(#,!*
( #%
)+!
$)06'(&*!$'("!7)*
''
8'("#2$
'''
9 ,!)*!

!"##$-$!&#+#$#.
)!'
+$)*
)
!'()*!$
.!&#+#%
.'+:
$)*#$!
#%)*!7'.
:-'+"'( %
&
"!

',
;!&#
)',!)!++'$





<<

8.a
October 23, 2023 Packet Pg. 234




















 






 





















 



!"
#








!











 


!
$



%



 

&













 

%
'

%









(




 
"



) ))


























*
















"

+
)

,
"-


 
















+










 






./01234567867879:98;:<<3=:>>3??92?@/?A2/>A?
BB 
%

CD&








 




 
,


E








E


 


B 






!(

8.a
October 23, 2023 Packet Pg. 235



























 




  







 






 ! "
#
$

  

 
 %

"
&
$

 




  ' 


 
 


"
(
) 
 



 






  ! *

+, 

"
-
$



'






' .  "
/01234567897898:;:5<;20=>0?1@ABB0?1:3B>0BC30DCB
"E



"F




 






G H'

.

  

  

I

 

  


J

K

'


  





  


'


"F






 
"
"L
  














M









 



 

 !  '




"N



"O




"P


 

*

+Q, 



"K
 

"F




8.a
October 23, 2023 Packet Pg. 236







!"#
!$#

"

!"##%

&"

&"'
()

'")

! *
#!'"(
+',-
!"&&"./+"
%


!"#0
("-#"'
#

" &)"
&-+" #!'"(
+')

'"#12+3!'"'#-
%


!"#%
3"
2+4"
&! ) 0+"&%
"!*%&"" 5678!
%"#
!!9+4"
&"'
'.++"
"##"'

!"##%

"
&
"
#&)-+5:8)""&'""2
'#!;5<8)""&
=!'"
!!!9+4"
&"'
'.++"
"##"'

!"#

&"' +"
+)

'"##%

&"

&"'=!&%!
>)&"" 56?8)""&)+0
(! &"+!+#!'"2+2"+&(
! "
!39+4"
&"'
'.++"
"##"'

!"##%

!
+2+
&"#
+"" ! *)"
&-+"#&%
&#&+-
&
3!"=#! & "!*%+! *(
+'#@
&"+
&"
(1

'#

2"#
+"" ! *#%

"2

"'

*
&%"#!'"2+2"+&(
! "#1=!&%#-
%

'#

2! *
#!#&! *)"3"+*+"" &+""#+%"'*"#
&%
&+"

%
0 &-+"%"!*%&)
&
"
#&>)&"" 56?8)""&
39+4"
&"'

!"#

&"' +"
+)

'"##%

&"
+

%0+"&%
>3"5?8)""&
! &&%"+"
+#"&

A



BCDEFGGE

H?

8.a
October 23, 2023 Packet Pg. 237










  















 


 !
"



#











!












#


  

!!




 
 #
!


!

!







 




 !

$%
!


$&%'









$(%





)





*

$+&%

 
  





,


 



-./0123456756768987:;<1=>?2@./A81@?.@B1.=B@



5

 



 



$%


C 





 #
 




 



DE

8.a
October 23, 2023 Packet Pg. 238














!
"#$
%&''"(#
)

!#*
'+
,-./"%
0%#1$(23(($#(
'"0

4 56+
$%&"0


4 5(+
$%&"0 %&''7
&2"282!
5#%(1#%$

,9/1

#&"!&2&)282(1:+
,;/
1 #


4 5(+
$%&"0 %&''"(#
)

!#*
'+
,-./"%
0%#2
& 8$
!1$(2#%
:" %
!
0$&!
#(#%
#(5(1#%
(+
$%&"0<"(#"'8!"0#%
$((1
'
2 "#

.=

8.a
October 23, 2023 Packet Pg. 239




 

 








 


  
  











 














 

! 


 




 






"

 




#




$




 

 
!%



&$

'
(
)*

% 


 

























+, 









 
 




-
 


 







 





 
./0


 


 1 


  



 
!
2 




  .
3 
0
2
(











4


5 











4







 





41 




 






6 




 






7 




 






82*

 

2
92:
 


 .;<0






 

9

 





 
 .<0






 



 

1 

 
 



1
3

!
%

 


%

 


 

%

 


 




%

 


 

%




 





%

 



 

(
 
=>

8.a
October 23, 2023 Packet Pg. 240







!"#$%&!"#
'()!&&!&&
*!'+,$+-"#
'*)++(
&!-!'+&(!+"
+-
.#/+/0)+
!--&#$!'"()!&&++1%#+/"
-
.#/+/
$% +'"!"#
'

!1%!&#2+//+(#3'+
$
'"!$"

$#"#'3(-+$#2$%#&/#'3$
/++1%#+ +'"(")!"'+$+((#"!"+")++,$+-"#
'
$

4 5+"!#&
#6&
-+/

(()!&&#'$
-
!"+! #'# %

+#3)"789:#'$):/++-+!.+("
$+!"+
()!/
*(!'/!///+-")"

!$!/+(;
!-!"#$%&!("<&+!(+/
'")+=$)#"+$"%!&6"<&+
6%(+$"#
')!(!

+!.+("<&+")!"#(/#

++'"

")#(("!'/!/>")#(("!'/!/
()!&&'
"!--&<
##4&!"

(>*)+'%(+/>()!&&#'$
-
!"+!/+$
!"#.+$
'#$+$
'(#("+'"*#")")+
!$)#"+$"%!&("<&+!((-+$#2+/#'=$)#"+$"%!&6"<&+6%(+$"# '!'/()!&&.#(%!&&<$!-
")+%#&/#'3!"! #'# %

")++7?9#'$)+(/++-!'/"*+&.+7@A9#'$)+("!&&
BC

:"
-D"#&#"#+(!'/E1%#- +'"

"
-%"#&#"#+(!'/+1%#- +'"()!&&+($++'+/<!
-!!-+"
!'(!/

(
")!"(%$)+1%#- +'"#('
".#(#&+

")+-%&#$#3)":

:*!<
AF

8.a
October 23, 2023 Packet Pg. 241







!"
#

!$%&#
'
(


!)*
+ *,%-%"")*
+#&'%#"&
%

-.

%/&.+0"&1%/* 2
%#* 0
#''!

!"3
*!

!+0"&1%*%-%""%#&'%#"&&!

-.%"4* +&.%/'#
% 4&.%"0** 0

5%6&%*
*!#''7 *
01'%8.0
5#
. *
9 &#'"'

5!

!"3#&'%#"&
%"#".".#''#-.
%2%#&! 8

-.*%-%""



!":
#/8

2 ;'+0''

"1%&!%%
01'%/#
%5'#""#*%/* .
1 &%<4#
2 %'

5.&
#//%#*#
-%
"%"
*%3+0''

"+0"&1%+#% 4
+%
"

#'+#&%*
#'/* =%-&

5 4*
& 4&.%
/#
%"
1 &.&.%

"
%#
0&"
% 4&.%!

!>6-%/&

"+#;1%5*#
&%&.* 05.&.%%"
5 *%2
%!/* -%""& #-- ++ #&%#'&%*
#&
2%!

!%"
5 - +/'%+%
&#*;& &.%#*-.
&%-&0*#'
"&;'% 4&.%"&*0-&0*%
?@

8.a
October 23, 2023 Packet Pg. 242





!"

#

$ % $&$'

!

"

(

)*+$

!",-,!,"(
!!.
&"
/-,%" "

%
!0,%
(

%

.& !/ %12
3 /

%/"(
!!-,%" "
,2$

!"
44,4

,
(
"
!
-

/
-(

-
&
!"
0!
)4

-(

-
&
!"
0!

2 %-
1& /
+,2
(
.& !/ %15,,2
%/1!
6 %1$

!,-,!,

7-!&/
/
%//,%,
-,&%

,8
/"
( "
9&
$
%
:(
2,!!,8 %1.& !/ %1
!
$
%
"8
(
$

!"
%/-,!,"-,&%

,8
/"
( "
9&
$
%
;

%.& !/ %1
<
%"-,
%1
: $8,=
>?7

,/,,"
>@

1 /,,"
> A
-,

>

!
$
%
" %-!&/ %1

!! "' ,%8,='4!
%

.,7
"'

-'

-(8
(

$ % $&$,2

%)BC+"9&

2 %"&2
-


*B

8.a
October 23, 2023 Packet Pg. 243








 
!"
#
!
$%" !
&!$'
"(!))*$+%#
!
$%" !
&$
,,
(
-!
!-+-!& ".
!& 
/012!
%$.
"- 3
!$)&

)
!
$%" !
&$
,,
" 
)
%"


". 
+!,)!
&+ $
,,#

'

"+
)

)%"
!
+
,
$ !& 
/012!
%$ "'
"(!)
3 !$)

''

%
%4 
!"
+$".'"
"+$-

!
,$*."
-."

!-$*',
$ !%*

)',5#"")
$$!)!
&-

!
,$!$
'
"!! )
)46,

!
&7!
% "
$
,,-
!

!

,!$ ".
''
"().
8 )

)
!--

!
,$*#! $+%,!$

%%$$!, " '+,!%
9: 
7
!,$
;<=

)$%
'7$!&
4.",,"#!
&$

)

)$

$+'',-

, " $

)

)$%"

!
)!

9
' 
0101/=

)$%
'!
&2
%"
>!% $!$ * $
!% 
$

)

)$
,,'
(
!,

?
"
@

)=

)$%
'!
&
!! !

A+!
).
"
5 )


*!-'
(!"+$$+
.
%$$
,,
" %)3. 5/BC2
'
%

!!D ,
$ 3. 5/BC2'
%
". 
A+!
).
"
5 )


$
,,%"
$!$ ".,

)$%
')
$
$'%!3)!
9
' 
0101/=

)$%
'!
&2
EF

8.a
October 23, 2023 Packet Pg. 244







!"##$"%#
&'#
!(
)
*

+#,&*#!
##$$% ((#-
.#
#! $$/#)*0#!*

1#)
*

23234546"##$7
89*-%
*
-:((#;
#*
(*-%
*
-$% (()
'/(<=*
%
%#/
.*$*

$
+1#)
*

232>45469*-%
*
-
!
*((&'*

*

7"%#+
((
=*
-$

! !$ #$&//(#'#

(

%##;*$
*
-$

! !$
!=%##
)

?*)
$#;*$
@
%#$
*)
#$

! !$% ((/#. *(
9
)
*

:
<(*-%
0;
&#(
)
#! (

-
%#/
%= <$$% ((

$
&)
:A:/
%
+
 .#(
B*-%

#$$1% ((

#;)##!+
&%&
!#!0+
<6C>47(&'#
$/#(*-%
0;
&#6#,&*. (#

D4E=

% (
-#
(*-%
&(7
!$%
&(!

#;)##!0.#6>7+

E)
!(#$*

<-*.#
$/


)A*#)
*


+##$

!*
-(*-%
0;
&#$@
%#(*-%
#(#'#

$$% ((#$)##
#!

'*
*'*F#(*-%

$/*(( -#
!)

0 #(*-%

%#$*
#
!!*#)
#! = <+
'
#*-%
$
*:((
&
!

(*-%
*
-@*
)(&!*
-*
E-
&
!E(*-%
*
-
!/ G*
- # (*-%
$@$% ((#(
)
#!

!!*#)
#! = <+
'=*
!
=$
+#$*!#

* (&
*
$

#!&)#(*-%
*'/ )

#$*!#

$
1&)%(*-%
*
-$% ((#!*#)
#!!
=
= !
! = <+
' !H )#

#$*!#
)#$
!/&(*)
*-%
E
+E= <
**"
'*
*'*F#
%#(*-%
-( #
!$/*(( -#@ ((= ((E'
&

#!0;
&#$$% ((#
*#

#!

-(#

= !$
%#-
&
!"%#
/
*' (
-(#$% ((##
=##
0+
<6>47

$#.#

<6547
!#-##$
***B
(( !(*-%
*
-&$#!

(*-%
= (G= <$
!

%#(
!$) /#+#
&#$$% (() $
*
$(*-%

!
=
= !
!1#)&*
<9*-%
*
-I

*

E )
*.
#!$#)&*
<(*-%
*
-$% ((

#) / (#
+#*
- )
*.
#!<

</#$

6$7*

%#/&(*)*-%
E
+E= <


!H )#

/
/#
<
DD

8.a
October 23, 2023 Packet Pg. 245





 






 

 !
"

#$%

#

&
#
%

 #


 
"
#

'
#


(
"
 &
)%##
"%
#) 

'

&
 
"
#

&
#' "
*



&
 
" #
''

 +

!,
# 

"!
 #
 -
'%
.! 
# 

!/ ''%
%

#!0
 '  %


'"
#
1





2
# 

#
#&

# '

 
%

%

#

%#

$ 

#"
*


3
4 $'
'

# 





'

$5%'


#
6)'' ) '"
#


'#2
#


#' )
#6 &
#
#

 )"

)%
 )
5
 )
#  

#  &
3
.2
#%

"
 #
# 
"# #%#

7


"
*'

')
#%
"
*

%#  
#





 


"
%#
# % %



5# 

#&

# '

 
%"
#
%

%

#
%#
"
*




3
89:;<=>?@AB@ABACDEF<GH9I=GI;<FJF<I9G;JFI9KLM<ND9NI<9GIN3 O/

 


 
"&



'$#

"
#


P
Q
''


#
#



#

  "#3
R


R
0


#

 
#'
''
#

# '


)

# 
Q# Q
$5%'#'''

#'"
#
Q

 #

##'!3
S

8.a
October 23, 2023 Packet Pg. 246






 !"#$
#%##&%
'&()

*'+""',(-

.+/*
*0('.)"+-"
'&('!"+"1%
+"/.+/
23+

"4.*5%+6-%'*
//+

"4.**!776"#

#
8"/
93+

"4.))+&-!"*:-%+6-%'*;*!776")"+#
''"/&

7.'&)+&

/"--"**'&))+&
"/+"*<
-+)&+'*
/)+=

*)-"*
>?#$
#%#&(&
"/+

"4.%)'&'4"
'.(""'4
/"
*)"+#
''"/'&*"+
"*

7"%

'3+

"4.*
*"+

'4&&+#&+"%

'**!776"'!"#

#%#4
/'!+"1%
+"/6.'!"5
'.@

""+
A?77/+

"4.*#%*'!
"#

#%#'4&,(&&',4
/")7
'"/+"&
"-!*
/"
B?77".?--"**?/"'-!"/+"&+-+)&+'
*)"+#
''"/'&!
"--"**'&'!"77".
(C
AD

8.a
October 23, 2023 Packet Pg. 247
 









 


 








 






 

 




 







!





"# 






!


 











$%&'()*+,-.,-.-/%0122)3144)55
678

7


9





















 !
 



!






!



!:









 



;


 


 



!





<! 
= 
9






>



 

 
8













!

?7


! 




!




!
;



 



 







!! 
 
!



 






@

8.a
October 23, 2023 Packet Pg. 248

 



   






  

 








   


 










 



!"#$#%#
& 



$'




 
 
!"#$#$#(
'

   '






   
)*+,-./012012134567*,,,8)69+:;<;6;8=,8)6)*=:*>:6
6?@AB@CB 6D@EE,F? +GAH@EFIJFGC? )FIAKFGLM
N  
'

OP

Q R ### R ### S
N  
'
T 
P
Q # # R#
UV
&


W

   








 

X
!"# YV
 


 
 





   Z 

[&

\  ]




^ 
 





^







 

 





 OPZ!U%P_`aP
QQ R#!"bZ!$"c$P_`WP
QQ R#!!Q
%

8.a
October 23, 2023 Packet Pg. 249


 






!

"#!#

$!%

 
 &%








!

"#!#

'  


 (

)*+,,-./+0123-,.3+4-,5-6-7028-1/915,:227-8-1/97,/915935,,2-.+;./0-9.*5-6-7028-1//<2- 9770=-5=+/*+1/*-3-,+5-1/+975+,/3+./,>?-./+01,@A>BC>BD@/*30:E*@A>BC>BDF23-,.3+4-5-6-7028-1/915 04G-./+6-,/915935,,2-.+;./0/*-H0770=+1E5-6-7028-1//<2-,9770=-5=+/*+1/*-I?3-,+5-1/+975+,/3+./,J 5:27-K-,L/0=1*08-,L915,8977M70/,:45+6+,+01,>
N>?+1E7-MO1+/P=-77+1E,>?+1E7-M:1+/5=-77+1E,9155:27-K-,93-,:4G-.//0/*-5-6-7028-1/,/915935,915 ,:227-8-1/973-E:79/+01,91504G-./+6-,/915935,0H/*-I?5+,/3+./L?-./+01,@A>BC>BFBLP-6-7028-1/ ,/915935,QI?5+,/3+./,L915?-./+01@A>BC>BCBR4G-./+6-P-,+E1?/915935,H03I?P+,/3+./,L915@A>BC>BCBL ?:227-8-1/973-E:79/+01,QI?5+,/3+./,>)*-;E:3-,+1/*+,,:4,-./+01+77:,/39/-I?5+,/3+./5-6-7028-1/ ,/915935,915=*9/3-,:7/+1E,+1E7-M:1+/5-6-7028-1/8+E*/700S7+S-> FA

8.a
October 23, 2023 Packet Pg. 250





!"#
$$%&'(&%)


!*#
$$%&'+&%)
,

+-.

)))/
*
0 $12
&)
),&*, *
,&*

+11$
2 &),$
'+$,)%&
,&*-.

)%0

),&*, *
3)/
45*%
) %
)65

)%&
789:9;96"
0 $12
&)

),&*, *
<45*%
) %
)
6789:9:965+11$
2 &),$
'+$,)%&
<45*%
) %
)
65 )%&789:9:9=-.

)%0

"

%'&5),&*, *
3 45"%
) %
)
,&*78>;>796

!*#
$$%&'+&%)
?.+&% ,

!*#
$$%&'+&%)

@/
A'+

%&)/%

+-

)%&%$$+
) ,)
,

!*#
$$%&'+&%)*
0 $12
&)
),&*, *
,&*#/,)

+$)%&'
,

!*#
$$%&'+&%)*
0 $12
&)2%'/)$B$%B

;C

8.a
October 23, 2023 Packet Pg. 251





!"#$%&#"'()#*(&"#+!
!"#$ &#",()#*(&"#+!*(-(!./0(&"#)) 12(3""."4(*(-(!./0(&")"+&*+,*)+&* ) //!(0(&"+!,(5 !+"#.&).6"4('*#)",#3"78(3"#.&)9:
;<
;=;7>(-(!./0(&")"+&*+,*)?'*#)",#3")7+&*
9:
;<
;@;78 //!(0(&"+!,(5 !+"#.&)?'*#)",#3")
A4(B5 ,()#&"4#)) 1)(3"#.&#!! )",+"('*#)",#3"
*(-(!./0(&")"+&*+,*)+&*C4+",() !"#&5*(-(!./0(&"0#54"!..D!#D(

<;

8.a
October 23, 2023 Packet Pg. 252





!!"#$
%&'!()*&%$
(+(!#,(&$

!!!#$-%&'!().&%$/(+(!#,(&$%--.01(2$$#$3(/(+(!#,(&$
-$ &/ 4/- &/#01(2$%+(-$ &/ 4/- &/-.,,!((&$ !4('.! $%#&-#5$3(0 -(/%-$4%2$.&!(--#/%6(/078 0!( 9:
;<
;=>;)?

83(6'.4(-%&$3%--.0-(2$%#&%!!.-$4 $(- !!!#$-%&'!().&%$/(+(!#,(&$-$ &/ 4/- &/ @3 $4(-.!$%&'/(+(!#,(&$%'3$!##A!%A(

B

CDDCDE B

CDDCD
FGHIGJIKGLLMFNHOLPHNF

%$(
$ &/ 4/-
Q%&%.R4#1(2$
%$(S%/$3
T5$
U
:;
<9

8.a
October 23, 2023 Packet Pg. 253







!!"#
$!%

#
&'()*+*,-./0123)2045..-
6-0'7'2).84679
:;<
&'()*+*,-./0123)20=.2
>.?0-'@08A0-10B2.CD)209
E<
F+)5G)B@H0)@I2'BG4.-* &'()*+*J+*K0-.C32.-)0DE
&'()*+*F+)5G)B@=0B@2I8C2:9BL'
302K'1MD
,-./0123)20NI0.?0-'55A-./012D)20)DD+K/0122.2I0D02K'1M-0O+)-0*0B2D.C2I0 K'D0G)D2-)12:

PBG)?)G+'5=.28C2:9
4-.B2 QRSTC.-A.-1I
3)G0 QUD2.-VA.-2).BW;SXUD2.-VA.-2).BWY
70'- Q<SRC.-G02'1I0G@'-'@0.B'550V
F+)5G)B@30A'-'2).B.C
Z02'1I0G[B)2D8C2:9
<
,'-M)B@'BG6110DD
&)B)*+*\'-'@0302K'1M
C-.*,-)*'-V4'1'G08C2:9
<
&'()*+*\'-'@0])G2I8C2:9X<S1.**.B@'-'@0DB.2?)D)K50C-.*2I0D2-002*'V'11.**.G'20 +A2.C.+-1'-D:
6110DD=.1'2).B6550V.-D)G0D2-002^I0-0?0-A.DD)K50:

F+)5G)B@_-)0B2'2).B
_-)0B2'2).B4'1'G0DDI'55K0G0D)@B0G2..-)0B22.^'-GD2I0A+K5)1D2-002'BG'

1.**.B1.+-2V'-G`)CA-.?)G0G:
aB2-'B10=.1'2).BNI0*')B0B2-'B102.0'1I@-.+BGb..-G^055)B@DI'55K0?)D)K502. 'BG5.1'20GG)-0125V.CC'1.**.B1.+-2V'-G.-G)-0125VC-.*2I0
D2-002:
[D'K50_A0B3A'10
&)B)*+*,-)?'20_A0B3A'10
8DO:C2:A0-+B)29
ERR
&)B)*+*>.**.B_A0B
3A'108DO:C2:A0-+B)29
XRR
&)B)*+*H.-)c.B2'5Z)*0BD).BD
\-.+BGb..-`1.**.B8C2:9XR
;X

8.a
October 23, 2023 Packet Pg. 254







!!"#
$!%

#
&'()*+,(('-.'/01234526789
:1;<(*=45267>
?++/2/(*1;@21*+1'+A
B/*/C)C?C()*2(5
D1*+A<1./*E4.3'<3*2(5A/237
FG
B/*/C)C?C()*2(5H*<;(A3+
I3'A(*1;@2('1E34AJ65267
K9
L

M

H6:)*E1;(NO()'2P303;(.C3*26:)*E1;(N<()'2+303;(.C3*2/AA)QR3<22(2S3+303;(.C3*2A21*+1'+A 1*+A)..;3C3*21;'3E);12/(*A(52S3Q1A3+/A2'/<2)*;3AAC(+/T3+Q=U1Q;38K69V69>9WH6US3TE)'3A/*2S/A A)QA3<2/(*/;;)A2'123Q)*E1;(N<()'2+303;(.C3*2A21*+1'+A1*+NS12'3A);2/*E+303;(.C3*2C/ES2;((X ;/X36
VF

8.a
October 23, 2023 Packet Pg. 255





!
"
#$%$!

&'()&(*+,*-,.
/'+'0102-34)5(&'()6',(7
89(:;
<==
/*>'0102-34)5(&'()?@33-
A-)*B*('38?AB;
:CD
/*>'0102-34)5(&'()E3(
F3G)-*H)8I)-5)+(39.'();
JD
K1'@,'+HL)'H7(*+,?3-0 /*>'010M10N)-39&(3-').O
/*>'010K1'@,'+HE)+H(789(:;+P*
&)(N*5Q.
2-34)5(&'()R7)3G)-*@@I-34)5(.'()'..1N4)5((3(7).)(N*5Q-)S1'-)0)+(.39 (7)N*.),'.(-'5(:

T+,'G',1*@E3(89(:;
?-3+( <=UV93-I3-57
&',) <W.(3-XI3-('3+YCUOW.(3-XI3-('3+YZ
B)*- <DU=93-,)(*57),H*-*H)3+*@@)X
K1'@,'+H&)I*-*('3+39
[)(*57),\+'(.89(:;
D
2*-Q'+H*+,A55)..
/'+'010]*-*H)&)(N*5Q
9-302-'0*-X?*5*,)89(:;
D
/*>'010]*-*H)6',(789(:;ODU53003+H*-*H).+3(G'.'N@)9-30(7).(-))(0*X*553003,*() 1I(3931-5*-.:

A55)..E35*('3+A@@)X3-.',).(-))(^7)-)G)-I3..'N@):

K1'@,'+H_-')+(*('3+
_-')+(*('3+?*5*,)..7*@@N),).'H+),(33-')+((3^*-,.(7)I1N@'5.(-))(*+,* 53003+531-(X*-,`'9I-3G',),:
a+(-*+5)E35*('3+R7)0*'+)+(-*+5)(3)*57H-31+,b33-,^)@@'+H.7*@@N)G'.'N@)(3 *+,@35*(),,'-)5(@X399*53003+531-(X*-,3-,'-)5(@X9-30(7)
.(-))(:
\.*N@)_I)+&I*5)
/'+'0102-'G*()_I)+&I*5)

8.S:9(:I)-1+'(;
<D=
CC

8.a
October 23, 2023 Packet Pg. 256





!
"
#$%$!

&'(')*)+,)),(-./(

0.12/
345,67,819/1.9,:';/;1<12/(89172,*98=19;
&'(')*)>,9'?,(817@')/(<',(<
A9,*(;B,,9C2,)),(D68EFGH
A9,*(;B,,9C.9':18/D68EF3H
I172,(=D68EFJ
K;;'8',(17081(;19;<
&'(')*)K),*(8,6
L1(;<21.'(MD./92/(8,6<'8/F
G4
&'(')*)K),*(8,6N(27,</;
O/9<,(1708,91M/D<PE68EF
QH
RS

SST
U4

8.a
October 23, 2023 Packet Pg. 257
 




 



































 !"#




 






 






 





 $$

%&'()*+,-.,-/-0123)4)(567)8%9%&83&:39;%5<8=5>9)?
3)4)(567)8%
9@ABCADC%EFBGEHIJ
K
K

L
M
K
N
OP

LQ
M
K

R
SORSP


LQ
M
K
T
U


O



P
VW
X
Y
  LQ
Z

K

V
LQ
X
T
 OP
W
K
$

M
K











$
[









\

TOP

]!
K
O







P

#

^ ]"#

^

S

W]




X
K



_
OP
W
M$R

L
`
K
$
M

OP
W
LQ
`
N OP"W]














R

TR













X
a

a
















b


c

8.a
October 23, 2023 Packet Pg. 258







! "#$"%&'
()*+,)-./0-,*10)23.4,1).)*+,)-.*0.,-35+06)7800+79.::1)5;3,::<.=1;1<:.*0 ,)7:0-,*.771+.-*:>0??,-0440)-06+*>,+70+71+.-*:>?+04*3.
;*+..*@
A;,<:.BC.)DC,-.

E1)1464F+1=,*.BC.)DC,-.

G;H@?*@C.+6)1*I
JKK
E1)1464L0440)BC.)
DC,-.G;H@?*@C.+6)1*I
MKK
E1)1464N0+1O0)*,:P14.);10);
Q+06)7800+R-0440)G?*@IMK
Q+06)7800+RC+1=,*.G?*@ISK
T,:-0)>G?*@IU
V771*10),:D*,)7,+7;
E1)1464V406)*0?
/,)7;-,C1)5GC.+-.)*0?;1*.I
JW
E1)1464V406)*0?()-:0;.7
F.+;0),:D*0+,5.G;H@?*@I
XK
GB+7@SWYYG(Z3@TGC,+*IIRMKMK[B+7@SWJUG(Z3@TGC,+*IIRMKSX\B+7@S]XKG(Z3@TGC,+*IIRMKSW[B+7@S]JX^] G(Z3@VGC,+*IIRMKSSI
_`

__a
]U

8.a
October 23, 2023 Packet Pg. 259








 
 



 


   

 



 !
"
# $ 
 
 
%
 


% $



$

&& 
'(''('


 
 



 

  



)**
'('+



 *



"
,
+



  - 
 $

,


 !



./012013.456789:;<=><?>@ABCD:CEFGHBI

  
 



 ,
+ 



 *+



J,
 

   


 
 
(


K %  $  
 ,
 
 


  
+  



8.a
October 23, 2023 Packet Pg. 260






!!
"#$
$
%&' (')*(
+'*),"
(&!
-
++$ %
.

.
(++')*
%&' (')*/'.$&)'0
(
1++')*)(
.'#& .'")."*'

.$
!!

)#
",+')*
2&)'.(

"!1
).

3 3&' (')*4
'*$./'.$').$

").)(

',.

)

.",.$
3&' (')*
$
1-'1&1$
'*$.+$ %

1 +&

(+')('#.
(')
#.'")

5 6
7
+&
')*$
'*$.89/'.$)"1"

.$)./
).:2
'*$.7; 8
,

..".$
$'*$
+.!"').",.$

"",+.
&#.&

,
"1.$
"/
+.0)'+$
(*
(

"
%&' (')*+ "#.
(').$

4' +'(


:<")')*('+.
'#.9

,

."=$!.


;74' +'(


:'+.
'#.8

=
'(

.%#>-#
!.'")
"
".+
++.$)0,.:76
8,

.')/'(.$9.$
1')'1&1*
"&)(2?""
+'(
+
.%#>
+$ %
1')'1&1",.
)7
8!

#
).",.$
"./'(.$"
.$

758,

.9/$'#$

'+*

.


!!

."
: '*)1
).


$
&!!

+."
:1: '*)/'.$.$
"/

+."
:..$

@&'

( "/

+."
:0

7682,"".+
.%#>&!
.".$'
.:75
8!

#
).",.$

)*.$",.$
"/

+."
:
$
1-'1&1.$'
.:75
8!

#
).!
"A
#.'")
+$ %
1 +&

(,
"1.$

/ ",.$
"/

+."
:
):/')("/ "#.
(").$
!
"A
#.')*
!"
.'")",.$
%&' (')*+$ %

'.$

#

+."
:/')("/"
+$ %
* <
(9.').
(9
.#$
(9,
"+.
(9
"
.

.
(')):+'1'
1))

.$. '1'.+
'
/+').")(,
"1.$
/')("/

;
B$

.$
*
"&)(?""
'++
.%#>.
+.+

)7
8,

.,
"1.$
!
"!

.: ')

9.$
&!!

+."
:
1: '*)/'.$.$
"/

+."
:,"
.$

).'

)*.$",.$
%&' (')*


.

.'(

.%#>+")".+/'.$

+
(
").*

$

-.

'"
+'(
+
.%#>').$

./
).:20

!

#
).",

+
(#"
)

".+$ )".%

++.$).$
,
").:
(

@&'

("

-'+.')*9/$'#$

'+

++9").$
(A"')')*>
: ".

C

8.a
October 23, 2023 Packet Pg. 261








!"#$%&'()%*%+(,-.'/-0/10+231*456%7%+
8!.('%96/--(-,
:!;-'1<63&/'(3-/-0+'1%%'&3--%&'()('<!
/!;-'1<=3&/'(3-!>?%51(-&(5/6%-'1<'3,134-0@A331B+'1%%'@2/&(-,0456%74-('++?/66#%63&/'%0 /-031(%-'%0'32/&%'?%/0$/&%-'54#6(&3151()/'%+'1%%'!
(!.'1%%'C3--%&'()('<D+%5/1/'%D*D@&3E56(/-'F/6GF/<213E'?%+(0%F/6G'3%/&? ,134-0@A331B+'1%%'@2/&(-,0456%74-('+?/66#%513)(0%0!
((!>?%01()%F/<+?/66-3'+%1)%/+'?%51(E/1<F/6GF/<'3'?%#4(60(-,%-'1<! (((!>?%51(E/1<F/6GF/<+?/66#%0(22%1%-'(/'%0213E'?%01()%F/<F('?'?%4+%325/)(-, E/'%1(/6+!*(22%1%-'(/'%05/)(-,E/'%1(/6+E/<(-&640%#4'/1%-3'6(E('%0'35/)%1+B +'%55(-,+'3-%+BA/,+'3-%+B31,1/)%6!
HI9/1G(-,/-0*1()%F/<+
/!9/1G(-,J8/1/,%D&&%++!9/1G(-,+5/&%++?/66#%513)(0%0/+1%K4(1%0#<.CLCC?/5'%1:M!NO P9/1G(-,/-0=3/0(-,Q!
#!*1()%F/<+!
RO

8.a
October 23, 2023 Packet Pg. 262






 











  


 





 

 




 !  
"







 #






$ 


 
%

$ 

 
$
% 


& 
 


'
  




(%
   (
$
$   (
$

')*$




 

'
$'
 ""'


 

  



 
 )'$

'


$
  
  





$
 
$


 
$$$



    +
  $

  





 

  

$$





 




(
 







$ 





,
 -
   

  
  
).  -
 
/   


$
 $
$
   

$
 
  $
 


 
(
&$
0


$
$
$
$

$
.  

$
   
 


$  


$
$


$ 1 2
"
 
$  
*


/

3   





     


$ 



$
 
$



 

%  

 

 

$
!'
  




$   
$
 
%
$  


$$

4

  
$
  2
5 

  
$  
'$



# 
  
$


  


 
$  



/



 
6  
  
  $


.  
     

$)$$





 $
 $$
  

"
"

7"
  





 


 
$ $




 
2
%  



 
 
 
$$
 $$
 
8 0

8.a
October 23, 2023 Packet Pg. 263






 
















 




!"#$%&'()'(*%+,--$.,//$0012"3-$42$5$-637$89
:;<=

>?

<

<<@
<
<



A






A
<B 

;<

@

<
C<<
<<<
@




D


<

@



@
E
F




@@<@<



G

H





 


I



H

<

<



D



J


D@

G


K
L
?


H

<
  

B

D<

<

<<
MAB
@ 
<@ 
@
N<
@





;<=
<



<












< 
O



 M<<<
@



>



<



@
<

G


 < E
P
Q <M 
D

8.a
October 23, 2023 Packet Pg. 264
 



  




 

 







 



 





 



!


"#


 
 
 






$%




  %
& 
 


 
'( 
)
& 


"

 

 

 



*

%
+,

-

)
& 


"

 

 











-

.
'/






%
%

 
)
& 


"

 

 


%


 







 -
 


0



$

% 


 %




 
%
%

 $-


%
 





 






 
 


.
'/

)
& 


 












. /




1



2
34

-0



5
$

 


  

-
.



 



-



)

6  


 %



%
*4

-



4

-

 




% 

 










 

-





%%


 






)
 


%
 
 



 %


 %




 
 








)
 

 



%


3

%



371


)
  
 








. /






2
)
  
 




+

'7
 
$





.




 



  $








6  
4


6  


  
 




 





3






 8









%


 


-





6  


  
 




+

-
 '9 
$









 %:

 %
 
 



 



%


3



+

 . /

 %
 
 




+

-
 '9 
$




 .





%
 
$










%
/3

8.a
October 23, 2023 Packet Pg. 265











 










  













!"


#







$















"
%


&
'


#













(



)



&


'*
%

+)
,
-
$.

*










$











/!0








#



$1













2





3








'
4





5


4
-
$



$




6

7 











6












63

$


$

$



8

$


$

$



9

$


$

$



,
:









;4



4" <4=




>?







<







#

?











3




3
5
'
*




*






*






*






*




 

*





 -


4



3

:
3
















5




5
#





#


5








:

4" 8






  


<<







3





.























 

$






"
$3

$







3








$

#







-$









  

>




3

@



A!4<0

B5
C4


5















5


 

<<3



2 8.a
October 23, 2023 Packet Pg. 266






 


















  









  
!


!


"
#

$


%
"
&

" 










  



'()*+,-./01/02-34(56746,89(:;6*<:,=6,>,:7<?,58
@@/
A
%
B









"




C!



"















!





D
"
!!










!
 
EE

8.a
October 23, 2023 Packet Pg. 267
 








 









 

 






 




 

 




 


 
 

 
 


 
!

" 
#

! 
 


! 

 



!

" 
$
 
 
% 
 
#
!&
'(  

')

' * '



 

 !&

 
! 



+,
" 

%  ! 
 

' 
! 
 


'


 
 + 

-
% 
 




 


!
 

 + 

' -




#  



 







 

!

 
 

  
#.
 * 


  



'


 

! 








/0*

123

*
#

! 








  
4
++3

%5 


 



'

673


%  " 








 -8,





-8,
" 









 - 4
++3


9267#
#
" 



'

 - : 
++,;,#
<
=>3  <

  
 




! 
'

: ++8,;,3  


 #

! 







 

!
5 


 



'

3 

- 


!





*

'

? 

:

 -@8,




- " '

,A!




 -'8A

 '


*  %

 
- 














-

 !
 

8B

8.a
October 23, 2023 Packet Pg. 268
 





 




















 


 


 


 







 
 



 

 






















 















 !"#$
 %"#



&




 













'
(



)
$ 








$ 



#






 



*+






,

-.-!"/" 0

'1

#
0

$


2
 

$











 







32



$  $








'
2


 



2
 



'
2



 









4
-#(


5#1 

6



$ -5#




*#)


$
$


7#8







$




 


9:;<=;<>?;@ABCDAEFGHGIGJAKLGCM;NOPQRPS@TUOV



 $


 $



$ 





 

 
 
-."7"%5W
!%

8.a
October 23, 2023 Packet Pg. 269










 !" #"$%!&$'()
*) !" #"(
+,-,./.01234567,648,96:;<=6>
+?@,./.01234567,64AB221
C14?D?6,2EACDF
G><ACD
+?@,./.01234567,64H26
I2J41?K4EL4154-62=M,64F
NOP Q/,B9,-KR4,K:6?-9A21. Q/,B9,-KR4,K:6S+?@,./. N<=446TM44?BM27456,2-G;>GUER,BBM,94VJ41B?WX,M61,56F Q/,B9,-KH4-K6:S+?@,./. GUO=446
746Y?5ZME+,-,./.MF
[-9,J,9/?BH26
A12-6 G<=6>
O=6>=21L215:
7,94E?LLBW626:44-92=
12\M2=?66?5:49/-,6MF
GSM621W?-9USM621WL216,2-]^=6>
NSM621WL216,2-M];=6>
CB641-?64_`=6>M46Y?5Z\,6:-2M64LY?5ZM
D4?1GO=6>T^=6>=21946?5:49K?1?K42-?BB4W
O;

8.a
October 23, 2023 Packet Pg. 270







! "#$"%&'
()*+,*-./012324*5-56
7042890,:-*4;
<;30=)*30,>?()*+,*-.2-,@*30A5,0;
B23C*-.2-,<880;;
D232.07553E*,49F
G2H*I)I JK6004653.232.0628*-.490;43004
<880;;L5824*5-<++0?53;*,0;43004M9030;)89*;135N*,0,O
@53,0N0+51I0-4;M*49-52++0?53;*,0;43004P2;*-.+0,3*N02*;+056 )145QK6004M*,49I2?135N*,02880;;45.232.0;O
()*+,*-.R3*0-424*5-
R3*0-424*5-@282,0;;92++>0,0;*.-0,4553*0-445M23,;4902,S280-41)>+*8 ;43004O
T-432-80L5824*5-U90I2*-0-432-80450289.35)-,V553,M0++*-.;92++>0N*;*>+045 2-,+58240,,*3084+?635I490;43004O

&
WX'Y'Y
Z'
G*-*I)IA5II5-2-,[53
B3*N240R10-/1280\10380-4
56;*40]
Q^_ G*-*I)I`53*a5-42+7*I0-;*5-;
D35)-,V553P85II5-JK64O
D35)-,V553P13*N240QK64O
(2+85-?\64O]U90;42-,23,;653490b/,*;43*84;;92++211+?O
 c
c"
X

! &
G*-*I)I<I5)-456
L2-,;821*-.*-490635-4?23,
\10380-456;*40]
^K_ T-8+5;0,B03;5-2+/4532.0d
G*-*I)I30=)*30,103)-*4
eK8)O64O
U5>0+58240,*-*-,*N*,)2+.232.0)-*4;P135N*,0,28+02323025624 +02;4fKK;=O64O*;135N*,0,653490123C*-.56N09*8+0;O<+403-24*N0+?P I2?>0+58240,280-432++5824*5-53+5824*5-;;03N*-.2++)-*4;*-490 ,0N0+51I0-4O
^g

8.a
October 23, 2023 Packet Pg. 271













!"#$%&$'()*$(+,-$,+$',+*./0',1'&2*1/.$3,**'.**,03,+*"#$%&$'(45+*617$6#6+*$(+,8+1%%9* 6*18#/*&18$'&$:1,*&$';*:,$0'<=4>?4>@>AB*18#/$'(+*$(+,CD-$,+'060/*,+1',-*',EF*$(+,AG=C 3**,,0,+*+$(+*8,H0$',03,+*/0038,/#:,#/*3/06,+*%0-*8,I'$8+*&(/1&*4.0/9#$%&$'(8%0:1,*&$',+* )$%%8$&*JK*/%1EL0'$'(&$8,/$:,D/*3*/,0M+1H,*/<=4<GA)$%%8$&*JK*/%1EN$8,/$:,C4 M4;,0/EO%$('6*',4
P>

8.a
October 23, 2023 Packet Pg. 272









  





 







 
 







! 
 



"




 

  




#








"







 
 






$
%
%

%


%
 



  
&






'( 

)







!*


 
%










 


+,"
&+
-






+&



-./
0 

- 1

&

/
0 

- 












"



 
 



 




&







 



 
/ 




 







&


 




&
%




 

%








- 


&

#

 #+#










 








&



&



 &














 


&



&
 
+ 

& 



 



&
%






%)


%
 &
'-..

+ &

.
23 #



.







&


 

-1411
 5'
.

0 

+ &


+ &





 



 




&







&

 
%



%







1 

 
 



1
 ' -


+ &
#



1 
 


6
 
+ &




' 
 
 


 &


&




7 

 
 




  



!

&

!
 

!

 
5
&+ &














#+#



&+ &





 



 




 &


 

 


 

&+ &












&


 



 
"
 


 
&+ &



 







' 


 







 
!+ &



&


















 8
+&


9 +
 












*

8.a
October 23, 2023 Packet Pg. 273
















 



 















 






!"




# 


#







$



 %




 


&!
 



 %


'
(
)
$


 



&*!

"


+
$



 %





% 
%


"%

# 




$,
$ 
-





#%




. !






%

#%
%"











-
 


&! 



 %
/
$#

0






1


"


%


 




.2!

3
"


%
%%
 $
&.!





"



%


 
 $
&.!



$,
$ 
$4




$%

# 

25 

,

64 

-""



# 

%


# 




"


#


$# 0

""


5 





%









"

%




$
.!

% 


%
(

7
"





"


%
%%
2!
"
'

#$



 

!
"
$
"





#


!
 

.!
"
8
 

.!
%



 


'


9 4

!
$

""
#





"#
0


5 

,

)

-""






$:
#

0


%

 %%


/%




5 

,

#




$








#- 






""


) 


$
:






"

%



& !

 


%

 

'

$
# 


(

 ;




:

!
<


%



9 4

!
$,
$
=.

8.a
October 23, 2023 Packet Pg. 274





 

 
 





 


  
 
  


 

 
 
































 



 


 


 







 




 








 








!


 





 






 




 
 

 


 




 
"#$%&'()*+,*+-./0%#12#3$2'4#$35678397%4'2':'17;<'36
=
 






 









>


 



 







 ?!@




 
  



 
 



 
A






BC
 
 



 





 

>

 






 

 
D
>

 




 
D
E

F
G
A
!
 


 
 
F

 EH



G
A
!
 


 


 






I
BJ



 


HK

8.a
October 23, 2023 Packet Pg. 275







 




 

 





 
 









 
 
 



 
 
 







   
 
 






  







!




 
"

 








 
 

 
#  

 











 

 $


%



 





 



 








 
  

&


'



(  

% 



)*+,-./0123124567,*89*:+9.;*+:<.:=->?@>;A=B?:CB,;.9.D.8BEF.:= %

#


%










 

  






 # 








( 

!# 



 


 


 

 








 



!
 

 











G!





GH!$
 


!
 

 










G!


 



I
JK

8.a
October 23, 2023 Packet Pg. 276




 

   




 


 
  

 

 
  









 



 

  




  






!
 

  




"
 


#


 




 



 

  #  $




 
  

% "& 


% " 




 




 "
  






 '


% " 




 

  #  $



 

 
 
  "
  


 
  


("

)



"


 "
 




*
"







#$



+
 
(

, ""

 


 










  


  
 "
  


+,
-
 
+ 

.

/  

 
 
 


 


+ 

0 



  1



(

 2+
 + 

.
(
/+
3
-
 42

5 6 +)+
* 3


 


 





"
 



 "






7  




   
 
 
 "8 



 



 









9









 #
 

"


  
 /



"


 

"
 :
 



6 
  


  


;


!

 

 
 


;

 




   

 

;
#"  

 ""


" 
 



%"  

 ""


" 
 


"  

 ""


" 
 



+

 # 







 

 






*
 


,<
=



 
 
 


 <


"" 



 

'




 







 #




 

#
 
:
/

3

 


3



" 
 

3


 

"
3


  "
3

 





 

3

  






6











#
  "
# 

"
 

  "
 

*
""



  :
 "
  



:

 

 




" 


  :
  

 


   "



,% 


>'

8.a
October 23, 2023 Packet Pg. 277








 



 
  

 







 

























 



 




 








 













! 

"


 






 

#

 $%


&
'
 ()&

 )
















)












* 

* +
* ,

&

,

$
 



 

  

 




 










 -

 




.
  






%



/012345678978:;<=0>?@=?4AB0CDA@=>E@2F4?4G4C@HI4>A
JK* 



 






 

  




 


 




L








  
 

 
MM

8.a
October 23, 2023 Packet Pg. 278
 








 










 
 






 




 


 



 


 
 


 
 

 
!

" 
#


! 
 


! 
 



!

" 
$
 
 
% 
 
#
!&
'  

(

) *



 

 !&

 
! 



+,
" 

-
 
 
 



%  ! 
 

* 
! 
 


*



  +. 

/
% 
 




 


!
 

 +. 


* /



#  



 







 

!

 

 

  
*#0
 ) 


  



*


 

! 









12)

3

)
#

! 








  
4
+.+.3

%5 


 



*

67
73


%  " 









 /1,




/1,
" 









 



 / 4
+.+.3


6



!

 *8




" 

67#
#
" 



*

 / 
9 +.+.,:,#

3  

  
 




! 
*

9 +.+1,:,3  



 #

! 







 


!5 


 



*

3 

/ 


!





)


*

- 

9

 /;1,




/ 
" *
,<!




 /*1<


 *


)  %

 
/ 














/

 !
 




  
  <
 
& 






 !
! !

 
 






9
 


 !!!





 
<<!
=:

8.a
October 23, 2023 Packet Pg. 279

























































!"










#


!






!






$
!
%

&
!



!








!


!







!

'!




!(




)




!




!


*


+,+

-

.


$

/



.






!
!
0


!














!







1
!




0

2




2


!





$!

0







!




0



!#

$!

0





!








!

3

+%!

4/



5






+4!



!


6&


!


!






78


!!







!


!





9:;<=;<>?@ABCCDCEF@GHIJKJLJEML
)1






!






!


















!










N


















'
!







!






2



.


1 
!


!







!
!


"%!
)











/$
!




!






!



'!




!
!




)



























!




!



0





!





!
!


'!




*O




$











2









!!
$
!
+,
7

2/











O%
$








+,
7
6O2$

%
$%
$
2






P,

8.a
October 23, 2023 Packet Pg. 280







!"!#$$%
%& '%()*
+,-,./.0123,456789:29;<=>>>-?@
+,-,./.012A,B2C6:29;D><>
E9F5G.,2H58/,G5.5-29IJG1J175B7.@KKK127/LB,M,7,1-7C@KKG58/,G52C5@JJG1M@K1:@N1-B,2,1-@K/75 J5G.,2,-N1.JK,@-N5O,2CPC@J25GQR9D>=S75F5G.,27=@-B@25-2@2,M5.@J,-N1.JK,@-N5O,2C2C5 3/LB,M,7,1-TGB,-@-N59
U9H58/,G5BU,-B,-V79W-@BB,2,1-2172@-B@GB/75J5G.,2X-B,-V7=2C5G5M,5O@/2C1G,2Y./72X-B2C@22C5 B5M5K1J.5-2,7N1.J@2,LK5O,2C2C5-5,VCL1GC11B@-B2C@2BO5KK,-V7@G5JG1J1G2,1-@25212C5K127,459 6TGB9QZD[6E\C9]6J@G2;;=<>QR^TGB9Q_DR`_6E\C9I6J@G2;;=<>QQ; a9IJJK,[email protected]@-B@GB793.@KKK127,-VK5c/-,2B5M5K1J.5-2JG1d5N277C@KKN1-:1G.O,2C2C5 B5M5K1J.5-272@-B@GB7@-B1Ld5N2,M5B57,V-72@-B@GB71:2C5L@75B,72G,N2/-K577.1B,X5BLYe@LK5 QR9>_9>[Dca9






!"!#$$%
f g$*
 f

f
*
!"!)
hi

8.a
October 23, 2023 Packet Pg. 281






!
""#
$
%"&
$

'()(*+*,-./0123(204(526789002
':;(*+*,-./0123(20<=..->-0:
?:2(.@<>?A
8BCD
':;(*+*,-./0123(20E.2F.G0-:H0
@I0-10)2.9J(20A
KDL M$"$
%N&$%O

P# ! ':;(*+*Q0(H62R79002
300:=J.3012(.)S7BSR@Q(==J(50TG0-=:UV(J2-(12A
':;(*+*W+(=5()HE0)H26@92BA)X:
&
Y
Z[\
,-./0123(20]60.G0-:==I-./012J(20(JJ+^/0122.260J02^:1_
-0`+(-0*0)2J.9260^:J05(J2-(12B
a)5(G(5+:=E.2
<-.)2 S892BbD92B9.-I.-16
3(50 Sc:)5RcJ2.-UI.-2(.)dC92B
KcJ2.-UI.-2(.)d792B
>=20-):2(G0dec92BJ(50J02^:1_9.-0)2(-0^+(=5()Hf(26).

J20I^:1_J
?0:- SD92BbC92B9.-502:1605H:-:H0.):==0U
W+(=5()H30I:-:2(.).9V02:1605
g)(2J
D92B

[$
%

ZZ&\\
h:-:H0^06()5,-(*:-U<:1:50D92B
':;(*+*h:-:H04(526R892Bb1.**.)H:-:H0J).2G(J(^=09-.*260J2-002*:U :11.**.5:20+I2.9.+-1:-JB
>110JJE.1:2(.)>==0U.-J(50J2-002f60-0G0-I.JJ(^=0B
W+(=5()HT-(0)2:2(.)
T-(0)2:2(.)<:1:50JJ6:==^050J(H)052..-(0)22.f:-5J260I+^=(1J2-002B i)2-:)10E.1:2(.)]60*:()0)2-:)102.0:16H-.+)5j..-5f0==()HJ6:==^0 G(J(^=02.:)5=.1:2055(-012=U.99260J2-002B
\
Y"&k&
k
Z&
'()(*+*F.**.):)5X.-,-(G:20
TI0)3I:10@I0-10)2.9J(20:-0:A
SDL '()(*+*Q.-(l.)2:=V(*0)J(.)J
h-.+)5j..-m1.**.)@92BAR8
n8

8.a
October 23, 2023 Packet Pg. 282






!
""#
$
%"&
$

'()*+,-))(./(01234563789:
;2<=)+>56378?2@42AB?A32+,2(,A
$
$#

"

C
D0+0@*@E@)*+3)6F2+,A=2/0+G0+
3H46()+3>2(,5/4(=4+3)6A0348
I:J D0+0@*@E@)*+3)6K+=<)A4,
L4(A)+2<?3)(2G45AM76378
N:

O

O #

&
P
QR
O

$&&
P
QR
S
O

$&&
P
QRTS

U9

8.a
October 23, 2023 Packet Pg. 283






!"#
$%&$'&($()*+,-./&
$%&$'&('(0,,1234521267&
$%&$'&(8(9211.2:/.*5:2;2.2-<.64<:4+:.&
$%&$'&(=(>?34;462-<.4<:@+4:2<@&
$%&$'&(A(B/;/1-,C/<6.64<:4+:.&
$%&$'&(D(E*21:2<@:/.2@<.64<:4+:.&
$%&$'&(F(G4<:.34,2<@&

H HIJKL

MN
OPP"Q
ROSTU
VPWXY"
V

"!

!Q
Q
ZV

N
N
WP
N["W\

X[W!Q]
P\WV
\V
"Q
!
" \
N
^
X
_X
"
W_P"N!`V
`aPW
!"\ VbW!W`!`
N
Q
U
P Zb
!
\NPP"Q
WV
W"cMN
"Z

d
ZaVZ "
" \
N
O TU
VPWXY"
V

WV

#
ecfV

Za_P
N
WP
NW!Q"W\

X_Xb!bg!`NWgWVQ"[!
PaQ!`" P
V " !W!QdV
QW!`
VW""
W

Q
]
NQ
U
P Zb
!
!NPP"Q
"h
icfV
"
VU
W!Q
!NW!

W!^WVP "j"

!

NWVW

V[!
PaQ!`
"!W
aVWPNPP"Q
"h
^c^ !"
VU

N
^
Xj" Z
!"ZW

"W!Q"`!d
W!
!W
aVWP\
W
aV
"h
Yck
laV
NPP"Q
Q
U
P Zb
!

_
Q
"`!
QW!Q
!"
Va

Q!WbW!!
V
NW
V
"Z

"W!Qb!bg
"

N
Q"
aV_W!

\
m"
!`

VVW![!W
U
U
`

W
![W!Q"`!d
W!
!W
aVWPPW!Q\ Vb"W!Q\
W
aV
"ck
"Z

!W
aVWP\
W
aV
"!
N
Q
"`!W!Q
!"
Va

! \NPP"Q
Q
U
P Zb
!
hW!Qn
ocY
"`!NPP"Q
Q
U
P Zb
!

_
"
!"
U

m"
!`

VVW![U
]"[W!Q"`!d
W!
!W
aVWPPW!Q\ Vb"
W!Q\
W
aV
"cRTVQcpqrsRomNciRZWV
SS[tspu#TVQcpqvrwqRomNceRZWV
SS[tsppS

H
Hxyz{yxy|

ecMN
ZV U" !" \
N"
NWZ

VWZZPX
WPPP
"W!Q"

"
NW
NWU
W!WU
VW`
W\
ZV!
"P Z
\

]
!
XRtsS!!

!W!Q!!
}

!
N"Z
V

!
V`V
W

VcW!Q
P
"W!Q"

"]
NW"P Z
\
!!

!W!Q!!
}

!
N"Z
V

!
"
V

"

_W
~`VWQ
!
cMN
"P Z
"b
W"aV
QW

N
"

Z
"

Z !
_

]

! ZZ "

"Q
" \
N
_aPQ!`cMN
WU
VW`
"P Z
"NWPP_
Q

Vb!
Qa"!`
N

\ VbaPW"

\ V
N!^^

!prcsvcs€sY

Vb!!`WU
VW`
"P Z
cY
Z
!Q!` !
N
"
Z

\
N
ZV 

[
MN
YV

VbWXV
laV
W"aVU
XW!Q"P Z
W!WPX""
Q

Vb!
]N

N
V
N

ZV U" !" \
N"
NWZ

VWZZPX
W"Z

d
ZV Z
V
X VQ
U
P Zb
!
c
icMN
"
V
`aPW
!"bWX_

b_!
Q]
NW!XQ"
V

c‚!
N

U
!
\W
!ƒ

_

]

!
N

ZV U" !" \
N"
NWZ

VW!QW!Xa!Q
VPX!`_W"
Q"
V

[
N
b "
V
"
V

U
ZV U" !""NWPP
WZZPXcRTVQcpqrsRomNciRZWV
SS[tspu#TVQcpqvrwqRomNceRZWV
SS[tsppS
€t

8.a
October 23, 2023 Packet Pg. 284








 !"#!#$
%&'( )*'
(


'
+
,%--
*.
(/ 0
'(

(1
1*'
,'( ( 2'
*
+1(

(

( 
3

'
'
+
,-
(
'+*
0 

+*'

(4

5 
+-



(
(
*(
5*( 
' ( 0


(-0

,( 

*'+*
0 


66'
-*
7
()2'

(8


*-
( --+*
**-

(*(

0 *(-(

+'
-*

( --

*('
('


-1
( --
( -

+-2'

(
,(
(
(-
9)
*8

* --,
--
('-(


(
'(
( 
3

'
3((,
+-(



:
*
;0
(

,

(
(** --+--
*+*

(4

5 *
(


*(
5*( 
'
( -

1*
-<

**
01 --

-1
( ( 2'

(
,7
(

=>=?@A@B
;0-

((**CD*=EEFGEC83 %C(HHB?@=?ID*=EF>GEC83 %C(HHB?@==H JKLM##" !#!N$#!N
/ ,
--

2'

( --+
**
(

(
--
( 2'

(

1,

(

(
(

+
*
(*+1( 9
(1
0

'+'
-*
*

'-(

B*

5 --179O99 (=?@>
CP*
*83
0(

HB'-'
'-(



5 --1-
((( 1'*( (**

,(

(


%P*
*3
0(

 --'-(
( 


-*
('+
,
+-(
( (
*('--*
,('%- --+
0 **
*(
,1

*-
B
--(
B*


'B*

Q
'(

B*

*

(

(
,('
--+(
*
( *
-
683
(
(*(
00((

 --+(
*(
( 3((

+-(
(+
-
:
--
*B*'




*(
0( ('-((
(

*
(




+'(1
,( ;0
(

,

(

(**
1+--
*+*

(4

5 *
(


*(
5*( 
' ( -

1*
-
9P*
- --(
( 3((,
+-+-

'(*5--
(
-

(
( (( 


(*
3
(
,
(
-,
*0-

(


0*


:*R +-


(+

0*B- --
+
0 **
*

(

*'-,



(S3
(
(
0 (
B( 0
-'

,


(S3
(
(
-
(

(*B* '-
'(,
('
Q(
(

(
-
;%--
,( 
(
(-*(
+'*('
('( ( 05
 *0-
(( 
5,(C=AH
( --
(+

0*+11

0

'',

( 5--
(( 5,(

( --+-,('

0*+1

0

'',
*
1+*
('+*
-1
1+
1(

*0-
( 
(
8&
-

(
'*-
 ----1T
(3
(
-*,

*(
(

(
3
(
*

*U



(1'-(

--'*


((
( ( 
0 


,(

(+

(
+-
( 3
(
*
*U



(1V
&7-

(*+1*

,( 
( --
(3
*(
(1CF@H
(
P/ 
'(
*


*
,--
'(*5---
B3
((( (

,-
B --+
'**(

-

((  

* -- 0


'

'0('*
'
,(-(50CAH,(
WF

8.a
October 23, 2023 Packet Pg. 285






 





 





 




 













!

 "#$%
 



&



'
"
( 

 










 )


 *

$
(



 
 






 


+

, 



 

(


 
 ,


+



,
  


&

,
-



 












( 


 






 










 
.)"/0#1/.2
. 33,$4""3
5675879:9;<=<>?@A<BCDCEBFEGFD7
2H



 


 

 





,







,











 
,
 









I




,





,




 
,



 




 

  







 



 
 




 








,





 

,


,


  



 














 





 













+



 

 




 

,


,


 
 

JK

L

 K2(

M

 


,I
K

.




 
3
 , 



 


,



&

 
 

,*


,  


 





 

 



 

 KI


 
+




 

N   2


 
O&

 


&



,




 O&
,


 
 







+









(


 
 

2

 






,

 










,



I




,




K

,



K(


 ,






-




 
 




 








 

,







 





 
 







I






 
 






 O&.0P3





 





'
"2






K






 

 

.#443
I 
$






,





-
,


 ,
-
K



&
.P443
I 
02 











 


.",4443
I 


 




,

O





,



 

/



 










 


 




-






.2
Q
3 





R/

8.a
October 23, 2023 Packet Pg. 286














 !"!#

$%&

'





$
'()(






*)



$

(+
,
-

)

-
'$%
-$)-
 )



'
- .)

- )( 
)





(
$


+

'
)

))(


/-

(
)



)$ 
$

0







)))




*)(





)/




1
*)
)

(

- )(
)
)

()'
$
)

-
(
) 
!2-
 *)



(

- )$(
)3


(-
 


0
((0((-)
'-)




'
(
-)


)

$
)
$)3



.2

45

 

(
-
)
+)$

$
-


2

 )
))
) ()$

-




)-







)) 
$

+)
$6))( 

)
(
-
 *))
+(

 )

))

"#(
)
(((

)"(

)$6))
() 7

 

)(
)$)
))

8('



)0(
(((-)
(')
)
(

9

: #.
);'!#<9
:" =:.
)'!#
>?@>A@BCBDEFGHFIJHKLFJILMNIHNOHL@
P
)5


)

))$6&

()$+




)(
/
9-P
)5

*)



-)
)()

)
)(
)
0-"('

(
) 
)

-
)
 ))
)
)

'))
)
()(
! )
3
'
03
;


.-
4)*)$


-
)
%

(

 )

)
 
(
)')
 )
(
'0(

$


-
))-



)
)( !#((

)


)(



(
)$


()
)
)


+)-
)
)
$6
-
 
(
) 
)



2&


$6*)$


(()
)
))$6



(
-((
)
 )
(
$


-
*)
()

(


')
 
'



+
-
)
)
$6-
 
(
)

Q

8.a
October 23, 2023 Packet Pg. 287





!"!#
$%&'(
)(*$+
,"-&+
!(./
&00&$
!+
1 2
3+
$
$%&--"$2&,

4-
2$ 5 22+/

+
/&--"+
-
1 &+-
&+ !

2+/
2 -- %
!6
!6-
7+ $'
-
5 !+84
5 !
5 1
#+/$ "6/+/
"
2 !6-
7+ $'
-
5 !+894&'9
$
,

9+
04&,:9

$/&!69-&!#,&0
!69&!#; $ +/
$5
&! 2/ $
1 !+&-&!#

$+
,&-&$+
,"-&+
!(+
./

!+
!+ 2+/
$
6"-&+
!
+ ,$
&+
,/&!6
!6/&# %-
!
&!#+ 4$
&:"05&

2 $5(
<(= "!#&+
!>

6!(./
"
25"-+
7-

-2 "!#&+
!?@ $-

-
0&$&+
#4'&5
!
5"5 22 "$?AB
2 +B/&--4
+/
+&!#&$##

6!2 $$

#
!+
&-+$",+"$
"!-
&!&-+
$!&+

#

6!
!
-

!6-

6$&#
!6
&00$

#+/$ "6/+/
#

6!$

%0$ ,
&&00$ 0$
&+
2 $+/

+
4&
# !+ 0 6$&0/'9
-
$6
- 6
,, !#
+
!90$ +
,+
! 2 !
+
!&+"$&-$
"$,
&!#-&!#2 $59&!#; $0$

!,
25&+"$

+$

(9%
+/-
6$&#
!69
&00$

#+/$ "6/+/
#

6!$

%0$ ,
&5 $
&00$ 0$
&+
2 $+/

+
(
>(C!#
$@ $(*$
&4
+%

!+/
- %
+@ $&!#&00$

#D!
/
#6$&#
/&--! +
3,

#
3?EB2

+
!
/

6/+&!#/&--4
, 50-
+
-'
!,-
#%
+/D$
7$
+&$#&!+5&+
$
&-+ 0$

!+
30 "$
+ %
-#D$

/&1&$#(



FG
H(>
,:(I 0 $+
! 2+/
%&-:
!6"$2&,
2&#
,:%
+/

4-
"!#
$0
!!
!6"00 $++$",+"$
/&--

3,

#&/

6/+ 2
3?EB2

+&4

D!
/
#6$&#
(>
,:/&--4

!+
6$&+
#
!+ +/
&$,/
+
,+"$
2+/

4"
-#
!6?B/ "
+/$ "6/9&+5
!
5"59"
2 5
-&$4"
-#
!65&+
$
&-9#
$
,+, !!
,+
!+ +/
&#J&,
!+
4"
-#
!6@ $&++/
&5
-

-9&!#&-
6!5
!+ 2+/
#
,:
#6
%
+/+/
@ $4
- %?! ,&!+
-

$B9&!#/&--
! +&00
&$&&!&##7 !+ +/
0$
5&$'4"
-#
!65&(9&!#! +&00
&$&&!&##7 !+ +/
0$
5&$'4"
-#
!6
5&(+/$ "6/
KE

8.a
October 23, 2023 Packet Pg. 288


 


  

 
 




  









 








 





 

 









   




 
!

 


 



"

#
 
!

 






   
$





#




# 
#




#
 

# #








#
 

 

 %&'
()*'++' 


 




, 

 


#
,

#


 


#
 


 


$




  








 
 

-



   

 

 
$













-./
 


   
#




  !







  "


0 


12
*3+1
'1 
44#-+56
2
*.37*1

1 
44#-+4
89:8;:<=<>?@ABC?DE@F:

%"
G

 
G

 
 




H




 1*4


# $

#






6
-H

 ,
  




 




 


6

.H


 
##

 
1.4


 



!




'I  
J





!!  

#

 
 $

"



H
 K%


$0 


!

#

!


 

 


  

/








G

 
 



 












 
33#G

 
12
*.37*1

1 
44#-+4
LL

8.a
October 23, 2023 Packet Pg. 289






!"#!$#%!%&'()
*
+*)),
*-
,
.#
!"#!$#%/%0
(.-'
,+

1*
+(''(#
!"#!$#%2%34,
)5


'-*
+*(+,
#
!"#!$#%6%7
*
+8*,,#
!"#!$#%$%9*:*(+
'5*(
*,
*5
#
!"#!$#%;%9
1<*
+<
1<=)

#
!"#!$#%>%?
1<

1*
+
,,'5

*

#
!"#!$#%"%&(
@


.*(+#
!"#!$#%A%(

1#
!"#!$#!%%8
55 1)

,*
+)*#
!"#!$#!!%B(*<*
+(.,

1
,,

*(*#
!"#!$#!/%C
+(1(
'
+'
,

#
!"#!$#!2%D

-
,
.*

(

*
++(
48*.#

EFEGHGIHIJGKKLMGIGNI

0#0)),
*-
,
.#B<*
+*(+
O<


*)),.
*,,
8+4,
)5
*
+*++


<*=)*
+
=


1P

(*(*-.
)(

(5
(#
Q#R
(*,*
+*(+#
!#S',
),TC

U
+

*,Q'
,+

1#0
,V)**18*.V*
+((,*+
*
+8
<

<
-'
,+

1
5),=<*,,-
,,'5

*+8
<*



.

O*,*

TW'*((O

T*
+,*<
1(
'
+,4,+'(

1<<
'(
O+*(X
#?
1<

1+4
<*,,-)(
+-.8*<(*
+
4*
+*,T(
*

4(#
/#Y

(
+

*,Q'
,+

1#0,,=(

(+

(V+'(

1<<
'(
O+*(X
V<*,,-
,,'5

*+8
<
*5

5'5
O

T<*,OO

T*
+,
O,
1<#
2#&+(
*
TZ(

+?
1<

1#[
<5
=+T'+
(
V=(

(,
1<

1<*,,-)(
4 ++O
(*
'(

1<
5)+(
*

4 (

5
-.(

O
(

1
(*
V)'-,

+8*,X*
+
)
*(*
8 <**O,4,
O
,,'5

*

#
6#S*=
5'59
1<#?
1<

1*
+*(+<*,,

=+<5*=
5'5<
1<)
\+

<
O
,,
8 1*-,
>"

8.a
October 23, 2023 Packet Pg. 290




 


  




 

!
 "#
 !

 

$
 #  

!
 "#%
 !

 

&
' 
(

&
' 
)*

#%+
  !

 ! 
!



,


)- .
&
*
/
'



0



 -  
! 1

 
1

+ 


  +

 


!+ 2
!


3!/*
1
  



 !

 

 2 

 

!
#4

*
/

!*
-

 

*

5




6
&
' *1 
')7.)-
 


*

*
'
*1 * 3
( ! (
!.( ! 
!
*
' +
'




 *
 
* 



 4
!.)




!-

+
*
1! 
*
 !  



 !
*


*






3
 ' 


!
89 8.a
October 23, 2023 Packet Pg. 291









    

 









 













 
 !




" 

"





#
"
$" "%!
&'
(



)
 

 
!







*







)
 

 +
%

'

),





)"


 %
 
%

%
-



")


"
%


.$


( $



 
%



 



%

 
% *




,
%)%

%
-





 
%)
 






% 

 /010

2 



2 





 $
 

 








 


!





  


!
34






*

%

( %


 %
% 


5 %



6




7
(%
3567(4  %


( %


 %
% 


5 %


6





7
(%
3567(4  %


89:;<=>?@>A@BCBDEFGHI89JK;<=KLM=N
/O 7
 




)"



 




!

 


 


 


%%



%
 "

%
%
 

"%#
!
P0

8.a
October 23, 2023 Packet Pg. 292






 


  
 



 


 





 
   







 


  



 
















 


!


 








 

"






 

 #




!






 








 
"





 

 #


!

!




 

$










 

 
%&'





(


 









 
)




'

 

 
*+
, 
,

-


 
 







 


 




.


 




 
#'


 '


 




   







 
 

/0123*42/5#+/66
78116
9:;9<;=:=>?@ABCDE@FGEFD@HI?JG;
K






#


'

 


 


1*1L8*8+


K

(





&'
M 



'


)

K


)
N

O


 




















'

 
(



P



QQ
M/6
-

Q
M/6 &M/6

+



"

 







 









#
















 

R



 


)

K

)


  

*1

8.a
October 23, 2023 Packet Pg. 293








 




 


 




















  !

 "


"
#$
 
% 

 &










'''
(
 














) *




+
 





 



  



 

 












  
,

8.a
October 23, 2023 Packet Pg. 294












 












 



 

 








 



!


"








#









$%



&




'


(
)



 




*


$



&

 





+##
,
&

&












*



,



 && 

*&


*

&



*


-


$##.

$
/01234567587969:;20<=0>1?3@A4BC0@>D
E@FG75HI6JHE4KL7MENOFPQQRS955Q
#

8.a
October 23, 2023 Packet Pg. 295








!


 
"
# $






%

%

&' 

 $ 
()

& !*


++,-$
% $


,-$





 $


!. 
  

 

&
!-

&
.


 
#
 



! $
/

.&".
0
. 
/







+,-$
 



-

.-

$
 . !1$ -

,-$
.



.

.-$
.,-$
.

 %
.0' "#


.&

 
##
.

! $
.- %
.


-
&! 



&.
&.

 "

$

)

&$





"%  


$
!-

&+%

$&

2 "


&

!

- 

! -
,-$


34-
) &
4-

 &




! $#"! $
-

!"5%

& 





5 -

 

.0
&.

#".
$  -&!
6)

&"


!

#
! $
-
 &"5


 $%
1-



5 -

 

.0
&.

#".
$  -&!

- $"$

--




#
"
7 "#
! $

 -


8)

&"


!



%
$%$-$!
&




)

696:;<;.=



"
.%!

&



&!



"
- >!
!
&
$ "
-

,-

0

?3@.@A.

@B2

"2  #
C
 
&

$%
& !


&" !

23 $$
D A




&"&!
&
 #



  


!
 





-
-
. 

 
. $$-



-
-
E%
 $$-

!


$
-
F. -
 "

*%
1G
C& 
2

+

)
3
#
-

4
3 -
H 
.

>


369<;.G
3

>

.

-






)-


&"
 #

$ !
"

-
%


!
-

&
. 
&
! $
-


>
 





-


>

6A 
)

&"

!  " 
 !  


.


&

"
 -


! 


-


! $
/ 

& 
-

&.!.
#,-
 



8*
@

-
-

$-
 #





&" !
- .
 # 0.


)

&"
!  -

$

-
!
- .
 # 0.


."

-

,-#
$3
1
0!

&


!->



&",-$

I($

$$-


 $

" #
!


&"
.-

$ 
" 1

!,-
& !
-


&$ #

$
<*


)

&"

$



&
.
-

&

&.!,-
.

0! ! 
#

&J
&
-





&.$$
& -

&

$ 




 $

$%$-$ "
&E4
6<I9K<E+%EFF.
8;66F
9<

8.a
October 23, 2023 Packet Pg. 296









!  "
"# $
 %&
$"#' 
 (!
$#!) #!
'

 !
%
("
!("

#%
*"
!&# '!
# 


+
&
&!
,&!-
)

)#.'+#('.
&/"


%

)
&#



!
# #

!0#!' 
1'
(2



!3
' "

!-
%)
$+&%
(#'
(

$!&# "
)% .+
&

&0

+4
#5
"&-
%)
!&# 

'
"#
+
&#.-
0

!
'#"6##
'5
"&-
%)
!&# '!"
!

)

0 &0

+#%%
#"&!4
7#!"#%
8#!% #
!9))
)&&

0 + (:;<="&!+
& #!"#%
>!&0"0
(
"# (
#


(?# !
0""
!!

+
&
&
(# #"&
"


0 &'

:@;ABCDA:EF&:%#
==$<G;;=
CH

8.a
October 23, 2023 Packet Pg. 297


 

!"#$%#%!%&'()*+,#
!"#$%#%$%-))./012/./34#
!"#$%#%5%6,7,(1.)(*8/+/*7+#
!"#$%#%9%:,;'/(,<)1(=/7>+)10,+#
!"#$%#%?%&1(=/7>(,<'03/*7+#
!"#$%#%@%&1(=/7>/7A./,'B,,#
!"#$%#%C%D*013/*7*B(,;'/(,<)1(=/7>#
!"#$%#%"%E/040.,)1(=/7>#
!"#$%#%F%G7A+/3,.*1</7>#
!"#$%#!%%&1(=/7>1(,1<,+/>717<<,8,.*)H,73+317<1(<+#

I
JKLMNLOPQRQ

STU

VWVXWVYZ
[\]^_W
Z`Ta]bc]
`Wb]ccY\Z
d
``]c]b
WVYZ
[

e

\]Zf

g\]]`

b
WY

T
hTU
i`ejk
Z
TlbZ_W
Z`
WVYZ
[

e
\]Zf

g\]]Z]`

l]Yc
hmTnoTopoeSqhrs^_W
Z`t
e
u]Zf

g\]sU
i`ejk
Z
Tlb\]Zf

gZ_W
ZV
[
Z
]
vW

c
`

l]YchmTnoTopoeSqhrb]ccYb]V]Z_W
Z`[
Zbc]
`W

bZ
`
Z
]]`

l]YchmTnoTopoeSqwrs^_W
Z`t
e
u]Zf

g\]stbZk
Z
T
x-EDy!"#$%#%9%A-z!{|:y}~:y€GA‚xy&-:ƒ6‚&-„y‚
†‡y€A~‚y€‚x:„x‚
D17<~+,:,;'/(,<&1(=/7>‚)10,+
^
`

]c
W`

]
`

eY`Z

V W

h\]\ZW

t

dZ`\]b]ccY\Z
d
``[
Z]bW

T
lˆ

ZV
ZY`Z

VhT‰\]\ZW


X

Z
`

]c
t[Šh\]\Zp‰o_W]Z[
^]
ch\]\Zpoo_W]Z[
^]WZ]
h\]\Zn‰o_W]Z[
nT‹
`WZ
]cSZk
Z
Ta]bc]
`W

b‹Sk
Z
b]cc\Z
d
`

\]Zf

g\]\Zˆ

b
W]
`_W]Z[
[

`WZ
]cW]Z]\cW

\]Zf

g\]\ZbZbW
`Z`_W]Z[
[

[Š
ZW
VZ]Z]T
wTtbZk
Z
Ta]bc]
`W

]cc`
Z
i\[
ZV
i`eW]
`

`WZ
]c]Z`
Z
b]cc
Y\Z
d
``]c]b
WVYZ
[

e
\]Zf

g\]]`

l]YchmTnoTopoeSqwrs^_W
Z`
t
e
u]Zf

g\]stbZk
Z
Tlb\]Zf

gZ_W
ZV
[
Z]
vW

c
`

l]Yc
hmTnoTopoeSqwrb]ccY`ZV

`Yvbk
Z
ZY]`W\

bZ_W
ZV
[
ZbV

V
c]Z
mŒ

8.a
October 23, 2023 Packet Pg. 298





















!" "#"$%&'()
*+,)
-./$0,
1)2,/3014
05 .6
)-,0),40

789+:;4<7::=>?7@=A8);BC=D;917DE=8F0G7?;:

H


 I

J 

K

L
MIH


 N




O



PHLMQ








O


R

O
O





ONSMMO

NM
OO
OM

OT 
H






O

U

VO
IR



L

L
RWNXNRSYTZYXZ

O




[


\
U


VO
I
]
^

L

L
RWNXNRS
U
_

V



Y`

P
a
OZ
L
Sbc






R 




 



d

















^
 
[






H







OR
M


O




 
 O
 






^






J
RWRb
U

_

P



e
MfOMa
 R





f

`

a


N





`
MIH



L
R





R




 




e
MfOMa
 Rc





f

`

a


N





L T VJ
]
O

^








g
T VJ
]
O

^








h 
 gMf
 J
N



O
M


R

c

R





 


i
H


 R



R

RS


H


 J

g
]
O

^








H


 J

i

 L

N



O
M


R

c

R





 


L
He
Sc





Wb

8.a
October 23, 2023 Packet Pg. 299









 !"#$
% ##&'( )&*!$+,&-$" -.&!/0 ($#
123456789:;<5=123456>?;@47??5A67B5C8?
@C44;D;?789EF79;
:6GCC4?H123456CF1F5I7B;
JK;FL<;<3;F?CMBG;?6GCC4KCK247B5C8N58642958D?B29;8B?HM7624BOH 789?B7MMP37?;9C8<7Q5<2<;8FC44<;8BR
@C<<285BOS??;<34OJMCF;76GTK;F<78;8B?;7B?58<7587??;<34O7F;7HCFJMCF;I;FOLU?VR MBRCM7??;<34O7F;7MCFDFC2K76B5I5B5;?CFWG;F;B;<KCF7FOCF<CI;734; ?;7B?7F;KFCI59;9R
@24B2F74X8?B5B2B5C8?YCFBG;7B;F?7897295BCF52<?ZJMCF;76GTK;F<78;8B?;7B?58<758 7??;<34O7F;7HCFJMCF;I;FOLU?VRMBRCM7??;<34O7F;7WG;F;B;<KCF7FO CF<CI;734;?;7B?7F;KFCI59;9R
[744;F5;?H453F7F5;?789<2?;2<?ZJMCF;I;FOJHUUU?VRMBRCM\CCF7F;7R ]BG;F;?B7345?G<;8B?Z7?9;B;F<58;93OBG;^5F;6BCFR
^7O@7F;@;8B;FJK;F;<K4CO;;K42?7995B5C874K7F_58D7?KFCI59;958BG; K56_=2K`9FCK=CMMK478F;V25F;9K2F?278BBC:;6B5C8JaRbLRUcUH^7O67F;R d;926B5C8?58K7F_58D<7O3;DF78B;92KC87KKFCI74CM7<58CF2?;
K;F<5BR
e<;FD;86O:G;4B;FJK;FbUU?VRMBRCM\CCF7F;7R
[CI;F8<;8B]MA6;?JK;FLUU?VRMBRCM\CCF7F;7R
fC?K5B74?789@45856?JRghK;F3;9R
X8?BF26B5C874:;FI56;?JK;FbUU?VRMBRCMK23456CF58?BF26B5C87F;7R :6GCC4?H123456CF1F5I7B;e4;<;8B7FO789<5994;?6GCC4?ZJK;F647??FCC<HK42?JK;FbhU?VRMBRCM CMA6;7F;7R
f5DG?6GCC4?ZgK;F647??FCC<R
:C6574:;FI56;Y76545B5;?JK;FbUU?VRMBRCM\CCF7F;7R
@C<<;F6574>?;@47??5A67B5C8?
S85<74@7F;H:74;?789:;FI56;?
[FCC<58D7891;B:BCF;?JK;FLUU?VRMBRCM\CCF7F;7R
i;88;4?JK;F;<K4CO;;K42?787F;7MCF4C7958D789284C7958D785<74?C8?5B;R j;B;F587FO:;FI56;?JK;FbhU?VRMBRCM\CCF7F;7R
SFB5?B?k:B295C?JK;FJHUUU?VRMBRCM\CCF7F;7R
S2BC<C354;`j;G564;:74;?789:;FI56;?
S2BC<C354;d;8B74?JK;FbhU?VRMBRCMCMA6;7F;7587995B5C8BC?K76;?MCF744I;G564;?MCF F;8BR
S2BC<C354;`j;G564;
:74;?789l;7?58D
JK;FLHUUU?VRMBRCM4CB7F;7R
S8O766;??CFO72BCF;K75FZbK;F?;FI56;37OR
S2BC<C354;`j;G564;
d;K75FHm7nCFCFm58CF
J?K76;K42?TK;F?;FI56;37ORJK;FbhU?VRMBRCM78OF;B754CFCMA6;C8 ?5B;R
aa

8.a
October 23, 2023 Packet Pg. 300









 !"#$
% ##&'( )&*!$+,&-$" -.&!/0 ($#
1234546789:;9<7=89
>?@<7AB
CD9EFGH@IJK3J4K?AL7AM44E@?89@N4KO=9N4E842AB9?E9?@J
P9EQ7=9P3?374ARD9E@9EQ7=96?LN7K@9EQ7=96?L@?E97A=82M9M4A@739JCD9EFGH@IJK3J4K ?ALE93?784E4KO=94A@739J
S?AT@?AMU7A?A=7?8
VA@3732374A@
CD9EWHH@IJK3J4KX44E?E9?J
S2@7A9@@P9EQ7=9@CD9EWHH@IJK3J4KX44E?E9?J
Y4559E=7?8Z9=E9?374A[@3?687@<59A3@\73<@9?37AB]CK4E9?=<RO^9M@9?3@N4ECK4E9Q9ELWH@IJ K3J4K@9?37AB?E9?\<9E9395D4E?EL4E54Q9?689@9?3@?E9DE4Q7M9MJ 13<8937==826@]CD9ECGH@IJK3J4KX44E?E9?J
S4\87AB?889L@]FD9E8?A9J
_?59=42E3@`9JBJN39AA7@a]FD9E=42E3J
P\7557ABD448@]CD9EFHH@IJK3J4KD448?E9?D82@CD9EGHH@IJK3J4K?E9? E98?39M343<9D448J
b3<9E=4559E=7?89A39E3?7A59A3?AME9=E9?374A2@9@]?@M939E57A9M6L 3<9c7E9=34EJ
[?37AB?AMcE7AT7AB[@3?687@<59A3@
S?E@:d7B<3
Y826@:e42AB9@
CD9EfG@IJK3J4KD2687=?E9?J
U288P9EQ7=9CD9EfG@IJK3J4K=2@3459E@9?37AB?E9?gA4D?ET7AB7@E9I27E9MK4E 423M44E@9?37AB\<9A@9?3@DE4Q7M9M9I2?834GHD9E=9A34E89@@4K343?8 7AM44E@9?37ABJ
Y4AQ9A79A=9:U?@3U44MCD9ECHH@IJK3J4KX44E?E9?J
U44MhE9D?E?374ACD9ECNGHH@IJK3J4K2@9?E9?D82@CD9EWHH@IJK3J4K4KO=9?E9?J U2A9E?8h?E84E@?AM
i4E32?E79@
CK4E9?=<RD9E5?A9A3@9?3@7A?@@9568L?E9?@ND82@CD9EFGH@IJK3J4K 4KO=9?E9?4ECK4E9Q9ELWH@IJK3J4K?@@9568L?E9?\<9E9395D4E?EL4E 54Q9?689@9?3@?E9DE4Q7M9MJ
e4MB7AB
S9M?AMSE9?TK?@3CD9EE445K4EE9A37A?MM7374A34D?ET7ABE9I27E9MK4EE9@7M9A37?82@9J j4398@?AMi4398@CD9E9?=<@899D7AB2A73ND82@F@D?=9@?Mk?=9A334E9B7@3E?374A4KO=9J 1MM7374A?8D?ET7ABE9I27E9MK4E?A=788?EL2@9@N@2=<?@E9@3?2E?A3@N ?==4EM7AB343<9D?ET7ABE9I27E959A3@K4E3<9?A=788?EL2@9J
i?7A39A?A=9?AMZ9D?7E
P9EQ7=9@
CD9ElHH@IJK3J4KX44E?E9?ND82@C@D?=9K4E9?=<X993Q9<7=89J
d2E@9E79@?AM_?EM9A
Y9A39E@
CD9EGHH@IJK3J4KX44E?E9?gCD9ECNHHH@IJK3J4K423M44EM7@D8?L?E9?J bKO=9@
mn

8.a
October 23, 2023 Packet Pg. 301









 !"#$
% ##&'( )&*!$+,&-$" -.&!/0 ($#
12345633758
9:;<6334;57=
>?6:@AA3BC<DC;<E;;:7:672?D;>AAFAAA3BC<DC
>?6:@GA3BC<DC;H6:>AAFAAA3BC<DC
I684J7=758K65D7=>?6:LMG3BC<DC;<E;;:7:67C
N7=OPQ5R=465D6=6>?6:@AA3BC<DC;<E;;:7:67C
97:O45SF92T=4J;:9:4H7D6>?6:7DD65875D3D7D4;5U457884D4;5D;DV63?7J63DV7D7:67H74=7T=6;5DV6 34D6WC
96:3;57=X6:H4J63>?6:@AA3BC<DC;<E;;:7:67C
Y6D74=X7=63
124=845SI7D6:47=3758
X6:H4J63
>?6:GAA3BC<DC;<E;;:7:67Z>?6:>FAAA3BC<DC;<;2D8;;:843?=7[7:67C \==]DV6:Y6D74=X7=63
X2TJ=7334^J7D4;53
>?6:@AA3BC<DC;<E;;:7:67C
>?6:MGA3BC<DC;<E;;:7:67<;:7??=475J6758<2:54D2:63D;:63C
Q5823D:47=_36R=7334^J7D4;53
R7557T43I4J:;T2345633>?6:>FAAA3BC<DC;<J2=D4H7D4;57:67Z>?6:>FGAA3BC<DC;<`752<7JD2:45S 7:67Z>?6:LFAAA3BC<DC;<843D:4T2D4;57:672?D;>AFAAA3BC<DC;:>?6:

GFAAA3BC<DC;<843D:4T2D4;57:67;H6:>AFAAA3BC<DCZ?=23>?6:@AA3BC<DC ;<;<^J6C
R;53D:2JD4;5758
I7D6:47=3a7:83
>?6:LFGAA3BC<DC2?D;>AFAAA3BC<DC
>?6:GFAAA3BC<DC;H6:>AFAAA3BC<DC
R23D;`I752<7JD2:45S>?6:LFAAA3BC<DC;<E;;:7:67F?=23>?6:@AA3BC<DC;<;<^J6C Q5823D:[Fb656:7=>?6:>FGAA3BC<DC;<2367:67?=23>?6:@AA3BC<DC;<;<^J6C Q5823D:[Fc4`4D68>?6:>FGAA3BC<DC;<2367:67?=23>?6:@AA3BC<DC;<;<^J6C Y6J[J=45Sd7J4=4D[
R;==6JD4;5d7J4=4D[X66X6JD4;5>eCL@C>fAFY6J[J=45S<7J4=4D463C Q5D6:`6847D69:;J63345S
d7J4=4D[
><;:67JVL6`?=;[663;5DV6`7g4`2`h;:O3V4<DF;:>?6:>FAAA3BC<DC ;<E;;:7:67FhV4JV6H6:43S:67D6:C
Y6367:JV758
K6H6=;?`65D
>?6:iAA3BC<DC;<`752<7JD2:45S7587336`T=[Z>?6:@AA3BC<DC;<;<^J6Z >?6:>FGAA3BC<DC;<h7:6V;2345SZ758>?6:eAA3BC<DC;<=7T;:7D;:[C X7=H7S6758N:6JO45S>?6:GAA3BC<DC;<T24=845S7:67?=23>?6:ACG7J:6;<S:;33;2D8;;:236 7:67C
N7:6V;2345S758XD;:7S6
RV6`4J7=FI456:7=F758
jg?=;34H63XD;:7S6
>?6:L6`?=;[663;:>?6:@AA3BC<DC;<;<^J67:67FhV4JV6H6:43S:67D6:C fA

8.a
October 23, 2023 Packet Pg. 302









 !"#$
% ##&'( )&*!$+,&-$" -.&!/0 ($#
123445675894:;<2=723
>?457=8723@:?3445
>?457=8
AB85CDEEE;FGH?G4H7587:B?4AEDEEE;FGH?GDAB85IDEEE;FGH?G4J85 AEDEEE;FGH?GDBK:;AB85LEE;FGH?G4H4HMN8G
O85;427K>?457=8A;B7N8B85PI;?457=8:2<?;DBK:;A;B7N8B85LEE;FGH?G4H4HMN87587GQ R<2<R:R4HI;B7N8;;97KKS8B54J<383G
694K8;7K<2=723
T<;?5<S:?<42
AB85CDEEE;FGH?G4H:;87587:B?4AEDEEE;FGH?GDAB85IDEEE;FGH?G4J85 AEDEEE;FGH?GDBK:;AB85LEE;FGH?G4H4HMN8G
U572;B45?7?<42DV4RR:2<N7?<42D723W?<K<?<8;W;8VK7;;<MN7?<42; X<=9?YK88?Z[7;83
>85J<N8;
AB85LEE;FGH?G4H4HMN8\4457587DBK:;A;B7N8H4587N9\88?J89<NK8G W?<K<?<8;D]7^45AH4587N98RBK4_8842?98K75=8;?;9<H?BK:;AH4587N9J89<NK8:;83<2 N4228N?<42`<?9?98:;8G]<2<R:R4HCG
W?<K<?<8;D]<245a428G
bcdefdfgfhijklminiopqrsmpqtukpvmnwd
QGx8;<382?<7KW;8;G
AG><2=K8ZW2<?T`8KK<2=;DT:BK8y8;DW5S7212MKKW2<?;723QNN8;;45_T`8KK<2=W2<?;Gx8F:<583 B75z<2=H457;<2=K8Z:2<?3`8KK<2=D3:BK8yD:5S72<2MKK:2<?D457NN8;;45_3`8KK<2=:2<?;97KKS8K4N7?83 42?98;7R8K4?7;?983`8KK<2={;|;85J83GO75z<2=;97KK24?S8K4N7?83`<?9<258F:<583;8?S7Nz;8yN8B? H457NN8;;45_3`8KK<2=:2<?;723H45?9858F:<583B75z<2=;B7N8<2?9835<J8`7_:2385?98B54J<;<42; H45K4?;<2?98x>Z}~42<2=3<;?5<N?G
CG@?985x8;<382?<7KW;8;Gx8F:<583B75z<2=H4558;<382?<7K:;8;4?985?972;<2=K8Z:2<?3`8KK<2=;D 3:BK8y8;D7237NN8;;45_3`8KK<2=:2<?;;97KKS842?98;7R8K4?7;?983`8KK<2=45:;8?98_;85J845<2 724HHZ;<?8H7N<K<?_7;B54J<383<2;:S;8N?<42V4H?9<;;8N?<42GO75z<2=;97KK24?S8K4N7?83`<?9<27 58F:<583H542?45;?588?ZH7N<2=;<38_753G
[Ga4258;<382?<7KW;8;Gx8F:<583B75z<2=;B7N8;;85J<2=24258;<382?<7K:;8;;97KKS8K4N7?8342?98;7R8 K4?7;?98:;8?98_;85J8D45<2724HHZ;<?8B75z<2=H7N<K<?_7;B54J<383<2;:S;8N?<42V4H?9<;;8N?<42G1HK4N7?83 <2724HHZ;<?8B75z<2=H7N<K<?_D7B75z<2=7=588R82?;97KKS8MK837;B54J<383<2;:S;8N?<42V4H?9<;;8N?<42G VG@HHZ><?8O75z<2=Y7N<K<?<8;GO75z<2=H7N<K<?<8;H45:;8;4?985?972;<2=K8Z:2<?3`8KK<2=;D3:BK8y8;D723 7NN8;;45_3`8KK<2=:2<?;R7_S8B54J<3834HH;<?8`<?97BB54J7K4H7R<245:;8B85R<?DB54J<383?98 H4KK4`<2=N423<?<42;758R8?
AGX4N7?<42G
7Gx8;<382?<7KW;8;GQ2_4HHZ;<?8B75z<2=H7N<K<?_R:;?S8K4N7?83`<?9<24289:23583{AEE|H88?D 7K42=7B838;?5<7254:?8D4H?98:2<?45:;8;85J83G
€A

8.a
October 23, 2023 Packet Pg. 303




  

























 









 






!


"#














$









$



 
%







&'
$
(

)




*













 






+








 

,









 ,

 
,


 




&
-.//
0%1


"
"
*&
-.23
0%
$


"
-4*&
-
4 0%$


"
-.+&
-
245

0%


"
--
6789:86::;<=>?@A<=B<CBD?A@<@CCBEBFGHIB@JDJ<@C<=CD8




%

  
%
,




 






,













#



 
%
,





 K


  

 L
(



M


































!






N




#

0








,









 















 














1)

#

)















!










*
-


,
 






 







)


"1
 
 



















2)





!







  
 



+

%





 
 

%
'






 
 

)





!







,









 


+

%





 
 

%
'






 
 
.)



 

 






!


$$


O
#






!



 
 '


 









 

'

 







 ,

 ,
 ) 

 



 






K

%
, 












PM
$

M

Q


 





R 



!












,




















 




 
S"

8.a
October 23, 2023 Packet Pg. 304





!"#

$ $%&'

$
$()&%*+(,

$-$,**(*.*/*'&(&*&00(''(&*

$1$'(/*(,2'(.*3(4&00(

$5$&00%*()23,&0*2(+&

$
$6&*(*./0(*('&

$7$%00)&83(4%&(('8&/+('(&*'*/,'

$ $%&'

9:
;<=; "
>
:"
:?;

="
@
!
>A
:

B @
"C >D
?E"C?!@?@F!"
=?
="G
:@
"H!?

@
=
"; !"BE

"<!@
=I?= <"
:?;

=" >
:

J !!HK=@!?!

L<B"
M<
!

:?;

=" >N=

E
OP;= I@

@

?E
@!> =F?
! !;=

@<=
"C?;;E
?
!"C?!@;
=F
"C!
E<@!HQ !!H?!@R
!
=?ESE?!

T
?!@
F?;?F
!@F
!
"C
"
?BE":F
!
>>

"C?!@
!> =

F
!
LU:
!
?==A!H <

:
=?""H!
@@<

"?!@
=
"; !"BE

"C?EEB @
"C?@F!"
=?
="C?!@ >D
?E"":?EE!

=;=

?!@?;;EA
:
;= I" !" >
:"

E
?"
F!F<F=
M<=
F
!
"?@ ;

@
F;E
F
!

:
; E

"?!@?
:

I

:

BV

I
" >
:

R
!
=?ESE?!L
WK=@LXYZ[\YW]T:LNW;?=
^^C_`XX^

$
$()&%*+(,

9:
; G
="?!@@<

" >
:
a
Aa <!
E<!@
=
:"

E
!
E<@
B<
?=
!
EF

@

:
> EE G!H#
NLa !"@
=?!@?@ ;
C=
V

=F @>A?F
!@F
!
"

:

R
!
=?ESE?!F?;?!@

T
;<="<?!

:

;= I" !" >a:?;

=X[LZYCNF
!@F
!
"
R
!
=?ESE?!C?!@ >
:

R I
=!F
!
a @
C> EE G!H?;<BE

:
?=!H?!@=

FF
!@
@?

!BA
:

SE?!!!Ha FF"" !L
bLa !"@
=?!@?@ ;
?F
!@F
!
"

:

J !!Hc?;?!@

:

T
>
:"

E
;<="<?!

:

;= I" !" >a:?;

=X[LZdCNF
!@F
!
"
J !!HK=@!?!

?!@c?;C?!@
:

R I
=!F
!
a @
C
> EE G!H?;<BE
:
?=!H?!@=

FF
!@
@?

!BA
:

SE?!!!Ha FF"" !L
aLN@ ;
H<@
E!
"> =@
"H!=
I
G;<="<?!

a:?;

=X[L_eCf
"H!g
I
GL
fLh
?=?!@@

@
;= ; "?E"
=
I i
;
=F
"C;<="<?!



!X[L_jLXY`Cg
I
?
! >;
=F
"C
> EE G!H?;<BE
:
?=!H?!@=

FF
!@
@?

!BA
:

SE?!!!Ha FF"" !L
]Lh
?=?!@@

@
?;;E
?
!"> =@
I
E ;F
!
?H=

F
!
"C;<="<?!

a:?;

=X[LZjCf
I
E ;F
!

NH=

F
!
"L
kLh
?=?!@@

@
?;;
?E">= F@

" !" >
:

SE?!!!Ha FF"" ! !<"
;
=F
"CI?=?!

"C?!@?!A

:
=;
=F
"
:?

?!B
?;;
?E
@C;<="<?!



!X[L_jLXd`CN;;
?E"L
RLh
?=?!@@

@
?;;
?E" !
!I= !F
!
?E@

=F!?
!"BA
:
f=

= =
:

SE?!!!Ha FF"" !C
;<="<?!



!X[L_jL`d`C]!I= !F
!
?E=
I
GL
hLN;; !
?!@=
F I
F
FB
=" >
:

SE?!!!Ha FF"" !?";= I@
@> =!9
E
_CN@F!"
=?
!?!@
S
=" !!
EL
OLN;; !
?!@=
F I
?

Q
!I E<!

=?!@?@
"H!;= >
"" !?E?"F
FB
=" >
:
g
"@
!
?Ef
"H!
g
I
Ga FF

L
eZ

8.a
October 23, 2023 Packet Pg. 305

































!
"
#$$
%&

$
'()*+),-,./01121304567849:;7<8<=;4>?@@2AA2?1)
B
C

D






ED
%%

D




F

GDB
H

C

D








 





H
I
#





J

D
D



G
C
"
D



#G
C

K#


HH



G
C

D

D


H

















D





J

D
D



L
M
"




D

N
#L



M
O#













D

&
PC

D

%
Q

R

S







T

%U
&
M
S


VD

J

D
D











D

W
C
O

GD

J

D
D





T

%U

&
X


RR




D
O
O

L

#




















 Y

T

%U
N&
#

R



 
X


O
X
HD


T

%U
N&
#

MJ






 Y


H 
D




Z

#
D
TD
[


H 



T
H

T

%U&N&



H
\C
D
D








H

D

%]
O
X
H
\^D

H


 Y

H
D

%]
O
X
H
M#
 
C

D

 
X


O

X
HD

]

8.a
October 23, 2023 Packet Pg. 306






 










 



 !"

##$
%&#
'()*+),-,./012/341567/0183./91/:;<==144//)>
?
@



A
@
B
 CC





 




B
 D
 






B
 C







%E$A
@
B
F

G






 

 
 


 



 

D  H>
"I 


@
 

?
@



A
@
B
 CC

 









B






%E$A
@
B
$





B





J
&

 !"

##$%&
H



 !"

##$%&#
KLMNOMPQPRSTTUVWXYZ[\[]S^T[VXZW_[`XS_M
?
 





 D

 CC
A
B
 C

A





aA



b#











C


D  H
"c


C


d 


$


 D
 $

C





D

C


 
eF




d 



C
C

 D










C


I





DD













 B


D


 

D

A



f

?









C


B



 
  D


 D  

B


 CC


  D

I CC ?
C



C


B

 D


 Dg



A




$

$

 D








h

#
AF

C


B


 D


C 

B
 D
 i




j

C

 D




k B

C





 lJEJ&$A


D
I
i

"
B
 D
C
m !

 
@
B

 D


C



D
 D
C







G 







 


$
B


 




 D
C


B
 C









n@
B

 D



 


C


B




D
 D
C



C 

j

C


C
C

k@
B

 D



 


C


B

C






 

!
C
D
C

B



D
 B
C

o
"



f
B
C



B


j

C



D


D


 D
C
 



 




B

pI


Ch

 CC


 



  
 $C

C

$




C

 

 
















FI


Ch

 CC


 


I CC  
 $




C

 

 CC 
















q 




B






%E$A
@
B

r@
D



C


I CC 

$s

 $




 





B

I CC 



 
EJ

8.a
October 23, 2023 Packet Pg. 307









    







 ! " 
#








  $ 


  




% &&
' 
(( ) %






 
) 




%





*  % "


)



! 

+ )
!  $
 
",
 ) 

-  % "


)



  





$%
%
%

 



 
.+  ) 

 


% /% 
 0 % "


)+

!
1

)




233
1

)


*% 
 

$ 0 )

0%



 0%
0 )

*
4&
54 67%

2
89:;<:=<=>?@A@BCDEA@AFGHIG?H:
% 1

)


 0 

0% +
$%% $
)$ 

 J
K 





  

L








 


 7

  


% &
M " 
N










   



% &
M " 

K 


  

L


 



2
&

#
L




+!   % "


)

$% 

%


% 0

  $
0 0   

0"


)

0
% 
)




6*% 
 

$ 0 )

0% +

*
4&54
67%

2
89:;<:=O=PQEEIHR?SHTUATVIQGW?HAGATFS?HDTXAFA?@FI@DIYYTIZF:
[\]^_`abcdbefegh_ij_k\l[mnhj[o
\ppqrsturvwvx\survwyvzw{rw
|}tpu~x\{r€vx]v{‚~sr€rvwƒ„t
~x\pp~tq]v{
 *
J#
 


1

)
 

2(/+
"


)



†3

8.a
October 23, 2023 Packet Pg. 308









!
"

#$
%"&'
(
"()%'

*+,%%
"(
-./01210/3/45.6789:;<=>?410@/51AB3..4.C
D5EE46645.

F4.51DG3.C06/53.
>2215H0IA01E4/
789:;<=>J5.4.C>IE4.46/13/51AB3..4.C
D5EE46645.

KL20KM5N?46@10/45.31LOP364QRPI4@43B>@/45.6
K100S0E5H3B78978<=>?410@/51AB3..4.C
D5EE46645.

T34H01U15E ?4E0.645.3B
V/3.I31I6
789WW<=>?410@/51AB3..4.C
D5EE46645.

A01E4/F5I4X@3/45.6Y
F3Z51
789:;J5.4.C
>IE4.46/13/51
S0H40M>P/G514/L5U[14C4.3B
A01E4/
D4/LD5P.@4B
A01E4/S0H5@3/45.789:;AB3..4.C
D5EE46645.

D4/LD5P.@4BVP201451D5P1/
K0E25131L\60
A01E4/6
789W7<=>J5.4.C>IE4.46/13/51AB3..4.C
D5EE46645.
?064C.S0H40M 789:]<=>?410@/51YS064I0./43B?064C.

S0H40MD5EE4//00Y51
AB3..4.CD5EE46645.

AB3..4.C
D5EE46645.51
D4/LD5P.@4B
F4.51\60A01E4/6789W^<=>J5.4.C>IE4.46/13/51AB3..4.C
D5EE46645.

D5.I4/45.3B\60
A01E4/6
789W^?410@/51AB3..4.CD5EE46645.D4/LD5P.@4B
?0H43/45.51
_`@02/45.6/5
[aZ0@/4H0?064C.

V/3.I31I6
789^b?410@/51AB3..4.C3.IK13.6251/3/45.

D5EE46645.

D4/LD5P.@4B
c3143.@06789W:?410@/51AB3..4.CD5EE46645.D4/LD5P.@4B
KL20KG100N?46@10/45.31Ld0C46B3/4H0>@/45.6
e0.013BAB3.K0`/3.I
F32>E0.IE0./6
789WbAB3..4.C
D5EE46645.

D4/LD5P.@4BVP201451D5P1/
J5.4.C[[email protected]
F32>E0.IE0./6
789WfAB3..4.C
D5EE46645.

D4/LD5P.@4BVP201451D5P1/
AB3..0I?0H0B52E0./
?46/14@/6
789WgAB3..4.C
D5EE46645.

D4/LD5P.@4BVP201451D5P1/
?0H0B52E0./
>C100E0./6
789W;?410@/51D4/LD5P.@4BVP201451D5P1/
];

8.a
October 23, 2023 Packet Pg. 309









!
"

#$
%"&'
(
"()%'

*+,%%
"(
-./01232456786-9:22324
;1<<3==312
;3>?;1@2A39B@C/.31.;1@.>
DE.F75G86HGDIJK7LDC:.>MMNOP55M
Q6

8.a
October 23, 2023 Packet Pg. 310





!"#

$%&'&"()"*#(+)#

, -%&'&"(.&/

0 .&/")%&'&"(#

1 (.&"(*(%.&/

2 !3%&'("&'

"(+!'")!3%&'&(4#

5&*&(4(+("&'")'&"((+6(+&(4#7!&+

8 9'"**!(&'&"(#

'"")".%#

))'&.+#

9&&"((+9(#&"(

, "+&6'&"(")".+%(#

0 ."'&"(")*&#

1 $%#

2 :(&"(#(++*&(&"(#

1 $%#

;<;==>?@>A<;
A?

@ABC


D;EF

G?
GHIG
GHJ
E
?>I
D
JKLM
FFH

GN>?


DM
FF




B?EF

G?

G
O
GF

OB=G
K


OB
>F?A@?==?>E

?
GE?
LBB



<
P<;==?>

OC


D;EF

G?
GI


<I


OBC


D;EF

G?
GF?A@
?==?>E
BN>?


DM
FF



@AQ>
D?LG
?==?>LBBN>?


DIK


<
R<;==?>

OIG
GI


<I


OBIG
GF?A@?==?>E
BN>?


D
M
FF



@AQ>
D?LG
?==?>LBBN>?


DIK


<S
T<;==?>

OJ
E
?>I
D
JKLM
FFI


<I


OBJ
E
?>I
D

JKLM
FFF?A@?==?>E
BN>?


DM
FF



@AQ>
D?LG
?==?>LBB
N>?


DIK


<
T<U<;==?>

ON>?


DM
FF



I


<I


OBN>?


DM
FF



F?A@
?==?>E
BMAM
V
>@AQ>
D?LG
?==?>LBBMAM>GW<
X<JDB

O;==?><;==?>
F?A@Q>E@AB?==>?
H@AB
L
G
O=G
=GAH
G@A?
A
BG=G

?DDGKE@A?E


B?

V@Y
?==?>V
EGB=G
K


OB
><
M<ZF[F
<\
>

BGL

=QE
?
G]EG?>>?LH?>>?==?>

B?>>@Q>E
LG
DLB


E?A

OBE?
OB?

HE


HF


H
GG

>V

OG
FLBBB?


?W
<^
BK

?
?==?>=G
E
E

??VGE?AHV
E?AH
G?
A
BGE?ABMA
>

EHB?==?>=G
E
B?>>
E
?B>


O@V



B
_

VK@V



E?A<
I<NG
EVG
<
P<]>
D<ZB?==?>
B?>>E
OABE


@
D?==?>E?
E
B?>>>?G>A?
E


>A
?
BG?

O
GB?==?><ZB?==?>
B?>>@?
F=?
E@ABG`VGEO<
aa

8.a
October 23, 2023 Packet Pg. 311


 















 


























 













!



 




" 

 #


$% 



 

# 












 

 












 


 





&

%
#'





%
# 




(

 





 

%
#






#



$ 

 %
#






























)





















*

%
#+
%
#


 




 






 


$!

)
 

 


  








#

% ,

)
)












%
-
.

/





%
 



 

 



.





%











 

#
 #



!#

)




0

















%













 


/








)
'
%

 


%
%'

12 34
5641&7188
9338
399

8.a
October 23, 2023 Packet Pg. 312




  !"#$%&'

( (
)*+

(
(,-./-,-0

(1(++-2343*56+-237-8+*3+-/-,--+

(9(
*.6)+:+-232)-6,-3+

(;(.**56+-237-8

(<(+-237-8.--

(=(>)-6?36-32+

(
(*36--*3+*5*7,

(
(,+:@--*3A@3+-*3+A364*6-?.-*3+

BCDEFDGBGHIJKLMND
OP#&!PQR" S &"QTU#&P &"P V &#W%S X# YQ%V!$ZRU#Q%! S X# YRS$! V[S "$ %&[S "PQ"% Y V X U$RZ %"&[RR$S"&"P \ % SQU]UQ%^&W$QU$_!S Q"#%WQX#TSQ%"R V &"S#Q%`Q%V"SQ%&#"`$S# %" V!$S Q%VV#&"#%!"#X % #WPT$SP$$V&Q%VV#&"S#!"&Y#"PQV#X S&#"a$_T[#UV#%W"aR &"PQ"RS$X#V !$%"#%[#"a#%&!QU Q%V!PQSQ!" SY#"PQRRS$RS#Q" "SQ%&#"#$%&bYP S % V VcOP &R !#d!R[SR$& &$_"P V &#W%S X# YQ%V !$ZRU#Q%! S X# YRS$! &&QS "$'
ec]S$Z$" f! UU %! #%&#" RUQ%%#%WQ%VV &#W%Q%V"P PQSZ$%#$[&QRR QSQ%! $_T[#UV#%W&Q%V&#" &g hci%&[S "PQ"% YQ%VZ$V#d V[& &Q%VV X U$RZ %"Y#UUT !$ZRQ"#TU Y#"P"P f#&"#%WQ%VR$" %"#QU V X U$RZ %"$_"P &[SS$[%V#%WQS QgQ%V
jc[RRU Z %"$"P Sj#"aS W[UQ"#$%&Q%V&"Q%VQSV&#%$SV S"$ %&[S !$%"S$U$_Q&R !"&$_V &#W%"PQ"QS %$"$"P SY#& QVVS && VcklSVcmnopkifPcqkRQS"rrbstmu'lSVcmvouwvkifPcekRQS"rrbstmmr BCDEFDGEGxKKyz{|}zyz~D
q &#W%S X# Y#&S €[#S V_$SQUURS$ !"&"PQ"S €[#S QR SZ#"_$S% Y!$%&"S[!"#$%bS !$%&"S[!"#$%b S PQT#U#"Q"#$%bQU" SQ"#$%b$S$"P S#ZRS$X Z %"&"$"P f" S#$S$_Q&"S[!"[S b&#" b$SQRQS‚#%WQS Qb f! R" _$S'
ecj$%&"S[!"#$%bS !$%&"S[!"#$%bQU" SQ"#$%&b#ZRS$X Z %"&bQ%VUQ%V&!QR#%W_$SQRS$ !"V X U$R V#% !$ZRU#Q%! Y#"PQRS X#$[&V &#W%S X# YQRRS$XQUgQ%V
hceVV#"#$%&$_ƒ$$SQS QY#"P#%Q% f#&"#%WT[#UV#%W %X U$R cklSVcmnopkifPcqkRQS"rrbstmu'lSVcmvou wvkifPcekRQS"rrbstmmr
jce&&R !#d VTa"P "Q" „QY j$ZRU#Q%! S X# Y#&S €[#S V_$SQ%aS &#V %"#QU#ZRS$X Z %"#%"P V#&"S#!"&"PQ"QS &[T !""$"P
lT !"#X q &#W%"Q%VQSV&$_"P &R !#d VV#&"S#!"c

(1(++-2343*56+-237-8+*3+-/-,--+

ec
&#V %"#QUq &#W%
X# Yj$ZZ#"" cOP
&#V %"#QUq &#W%
X# Yj$ZZ#"" &PQUU!$%V[!"V &#W%
S X# Y$_Q%aS &#V %"#QU#ZRS$X Z %"#%"P
V#&"S#!"&"PQ"'†
mc
&[U"&#%Z$S "PQ%"PS "P$[&Q%V&€[QS _ "$_ƒ$$SQS Qk#%!U[V#%WWQSQW &rQ%VZ "&$S f! V&"P ‡e
"PS &P$UV&#V %"#d V#%OQTU mucsˆctot`ekmrgQ%V
mtm

8.a
October 23, 2023 Packet Pg. 313



 



!"# $%%&$'$(
) $*+,) +-,
.&$$  !!,/$

01234
0320

516434
0370

8018434
0385

709
0380

83:;<=>;?@<ABC@<D>EC=>;?DFD@?;GDF@;H<I??JD?@<ABC@<=DFF@;KDL;GDB=<F<@MC?NKD@CD>I<N;@ ;?J<@EC=I@<?C;>D@ODFF@;KDLPO?J<QLD>>C>RS;MMC==C;>3

T3U3QLD>>C>RD>EV@D>=F;@?D?C;>S;MMC==C;>3VJ<QLD>>C>RD>EV@D>=F;@?D?C;>S;MMC==C;>=JDLLJDK< E<=CR>@<KC<WDB?J;@C?OG;@DLLF@;H<I?=@<ABC@C>RQLD>>C>RD>EV@D>=F;@?D?C;>S;MMC==C;>DFF@;KDLX=BIJD= I;>EC?C;>DLB=<F<@MC?=NE<KCD?C;>=;@<YI<F?C;>=?;?J<ZPH<I?CK<:<=CR>[?D>ED@E=ND>EKD@CD>I<=\3 U3S3:C@<I?;@3
63VJ<:C@<I?;@=JDLLI;>EBI?S;MFLCD>I<]<KC<W;GD>O@<=CE<>?CDLCMF@;K<M<>?C>?J<][EC=?@CI?= =BPH<I??;ZPH<I?CK<:<=CR>[?D>ED@E=3

8363VJ<:C@<I?;@=JDLLJDK<E<=CR>@<KC<WDB?J;@C?OG;@DLLF@;H<I?=?JD?E;>;?M<<?;><;@M;@<;G ?J<I@C?<@CDLC=?<EC>=BP=<I?C;>T;G?JC==<I?C;>G;@DE<IC=C;>PO?J<]<=CE<>?CDL:<=CR>]<KC<W S;MMC??<<;@=BP=<I?C;>TU;G?JC==<I?C;>G;@DE<IC=C;>PO?J<QLD>>C>RD>EV@D>=F;@?D?C;> S;MMC==C;>NC>ILBEC>R;B?E;;@EC>C>RD>E;B?E;;@@<?DCL=DL<=FB@=BD>??; [<I?C;>=6^3873620D>E6^38736503
7383VJ<:C@<I?;@MDO@<G<@C?<M=EC@<I?LO?;?J<QLD>>C>RD>EV@D>=F;@?D?C;>S;MMC==C;>;@ ]<=CE<>?CDL:<=CR>]<KC<WS;MMC??<<WJ<>C>JC=_J<@_?J<C@;FC>C;>?J<FBPLCIC>?<@<=?W;BLEP< P<??<@=<@K<EPOJDKC>R?J<QLD>>C>RD>EV@D>=F;@?D?C;>S;MMC==C;>;@]<=CE<>?CDL:<=CR>]<KC<W S;MMC??<<I;>EBI?E<=CR>@<KC<W3XZ@E3657`XaYJ3:XFD@?\\N806^bZ@E3627^c2XaYJ3TXFD@?\\N 8066\


← All documents from this meeting